CVE-2022-1811: Unrestricted Upload of File with Dangerous Type in GitHub repository publify/publify prior to 9.2.9.

Q: How do I fix CVE-2022-1811?

publify: upgrade to 9.2.9. Exact commands for each OS are on this page.

Q: Is CVE-2022-1811 being exploited?

CVE-2022-1811 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1811 affect?

CVE-2022-1811 affects publify. Severity is medium (CVSS 5.4). Unrestricted Upload of File with Dangerous Type in GitHub repository publify/publify prior to 9.2.9.

Q: How urgent is CVE-2022-1811?

Priority 38/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2022-1811 is a medium-severity flaw (CVSS 5.4) affecting publify. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Unrestricted Upload of File with Dangerous Type in GitHub repository publify/publify prior to 9.2.9.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Weakness	CWE-434
Published	2022-05-23
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: publify project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-05-23 16:16 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

publify project publify UPGRADE

Affected: < 9.2.9

Fixed in: 9.2.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy publify || rpm -q publify || publify --version

2. UPGRADE to 9.2.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade publify

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade publify

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1811?

publify: upgrade to 9.2.9. Exact commands for each OS are on this page.

Is CVE-2022-1811 being exploited?

CVE-2022-1811 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1811 affect?

CVE-2022-1811 affects publify. Severity is medium (CVSS 5.4). Unrestricted Upload of File with Dangerous Type in GitHub repository publify/publify prior to 9.2.9.

How urgent is CVE-2022-1811?

Priority 38/100. Public exploit reference

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2024-39311 MEDIUM 5.4 UPGRADE UPGRADE Publify is a self hosted Web publishing platform on Rails
CVE-2023-0569 MEDIUM 6.5 UPGRADE Weak Password Requirements in GitHub repository publify/publify prior to 9.2.10.
CVE-2023-0299 CRITICAL 9.8 UPGRADE Improper Input Validation in GitHub repository publify/publify prior to 9.2.10.
CVE-2022-2815 MEDIUM 6.5 UPGRADE Insecure Storage of Sensitive Information in GitHub repository publify/publify prior to 9.2.10.
CVE-2022-1812 CRITICAL 9.8 UPGRADE Integer Overflow or Wraparound in GitHub repository publify/publify prior to 9.2.10.

References

← Back to latest CVEs