CVE-2022-1793: The Private Files WordPress plugin through 0.40 is missing CSRF check when disabling the protection, which cou

Routine

MEDIUM 4.3DOWNGRADE

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

The Private Files WordPress plugin through 0.40 is missing CSRF check when disabling the protection, which could allow attackers to make a logged in admin perform such action via a CSRF attack and make the blog public

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-06-13
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: private files project

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

Am I affected?

Timeline

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

private files project private files DOWNGRADE

Affected: 0.40

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.40

1. Check installed version

apt-cache policy private-files || rpm -q private-files || private-files --version

2. No fixed release: DOWNGRADE to a release before 0.40 (Debian / Ubuntu)

apt-cache madison private-files sudo apt install private-files=<VERSION_BEFORE_0.40> sudo apt-mark hold private-files

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list private-files sudo dnf downgrade private-files-<VERSION_BEFORE_0.40> sudo dnf versionlock add private-files

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-1793?

private files: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-1793 being exploited?

CVE-2022-1793 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-1793 affect?

CVE-2022-1793 affects private files. Severity is medium (CVSS 4.3). The Private Files WordPress plugin through 0.40 is missing CSRF check when disabling the protection, which could allow attackers to make a logged in admin perform such action via a CSRF attack and make the blog public

How urgent is CVE-2022-1793?

Priority 29/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs