CVE-2022-4057: The Autoptimize WordPress plugin before 3.1.0 uses an easily guessable path to store plugin's exported setting

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

autooptimize: upgrade to 3.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-4057 being exploited?

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

CVE-2022-4057 affects autooptimize. Severity is medium (CVSS 5.3). The Autoptimize WordPress plugin before 3.1.0 uses an easily guessable path to store plugin's exported settings and logs.

Q: How urgent is CVE-2022-4057?

Priority 47/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEUPGRADE

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

The Autoptimize WordPress plugin before 3.1.0 uses an easily guessable path to store plugin's exported settings and logs.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-425
Published	2023-01-02
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: optimizingmatters

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

Am I affected?

Timeline

2023-01-02 22:15 UTCPublished CVE record published
2026-06-17 05:19 UTCUpdated Record last modified

optimizingmatters autooptimize UPGRADE

Affected: < 3.1.0

Fixed in: 3.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 3.1.0 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade autooptimize

Note

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

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: Autoptimize < 3.1.0 - Information Disclosure

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

autooptimize: upgrade to 3.1.0. Exact commands for each OS are on this page.

Is CVE-2022-4057 being exploited?

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

CVE-2022-4057 affects autooptimize. Severity is medium (CVSS 5.3). The Autoptimize WordPress plugin before 3.1.0 uses an easily guessable path to store plugin's exported settings and logs.

How urgent is CVE-2022-4057?

Priority 47/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs