cve.bz

CVE-2022-1810 publify project publify

4.3 mediumExploit referenceEPSS 0.8%Fix available

Medium (4.3) in publify project publify. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in publify_core 9.2.9.

Authorization Bypass Through User-Controlled Key in GitHub repository publify/publify prior to 9.2.9.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 59th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-1810 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-1810?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-1810?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-1810 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
publify/publifybefore 9.2.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c273-c6vg-4pv5RubyGemspublify_core<9.2.99.2.9

References

Check your stackJSON