CVE-2023-2113: The Autoptimize WordPress plugin before 3.1.7 does not sanitise and escape the settings imported from a previo

Q: How do I fix CVE-2023-2113?

autoptimize: upgrade to 3.1.7. Exact commands for each OS are on this page.

Q: Is CVE-2023-2113 being exploited?

CVE-2023-2113 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-2023-2113 affect?

CVE-2023-2113 affects autoptimize. Severity is medium (CVSS 4.8). The Autoptimize WordPress plugin before 3.1.7 does not sanitise and escape the settings imported from a previous export, allowing high privileged users (such as an administrator) to inject arbitrary javascript into the admin panel, even whe

Q: How urgent is CVE-2023-2113?

Priority 32/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2023-2113 is a medium-severity flaw (CVSS 4.8) affecting autoptimize. 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.7 does not sanitise and escape the settings imported from a previous export, allowing high privileged users (such as an administrator) to inject arbitrary javascript into the admin panel, even when the unfiltered_html capability is disabled, such as in a multisite setup.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Published	2023-05-30
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: autoptimize

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

Am I affected?

Timeline

2023-05-30 08:15 UTCPublished CVE record published
2026-06-17 05:51 UTCUpdated Record last modified

autoptimize autoptimize UPGRADE

Affected: < 3.1.7

Fixed in: 3.1.7

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 3.1.7 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade autoptimize

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-2023-2113?

autoptimize: upgrade to 3.1.7. Exact commands for each OS are on this page.

Is CVE-2023-2113 being exploited?

CVE-2023-2113 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-2023-2113 affect?

CVE-2023-2113 affects autoptimize. Severity is medium (CVSS 4.8). The Autoptimize WordPress plugin before 3.1.7 does not sanitise and escape the settings imported from a previous export, allowing high privileged users (such as an administrator) to inject arbitrary javascript into the admin panel, even whe

How urgent is CVE-2023-2113?

Priority 32/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-2635 MEDIUM 4.8 UPGRADE The Autoptimize WordPress plugin before 3.1.1 does not sanitise and escape some of its settings, which could a

References

← Back to latest CVEs