CVE-2022-4260: The WP-Ban WordPress plugin before 1.69.1 does not sanitise and escape some of its settings, which could allow

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

wp-ban: upgrade to 1.69.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-4260 being exploited?

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

CVE-2022-4260 affects wp-ban. Severity is medium (CVSS 4.8). The WP-Ban WordPress plugin before 1.69.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is dis

Q: How urgent is CVE-2022-4260?

Priority 36/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

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

The WP-Ban WordPress plugin before 1.69.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in 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.9% (top 42%)
CISA exploited list	No
Published	2023-01-02
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp-ban project

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:20 UTCUpdated Record last modified

wp-ban project wp-ban UPGRADE

Affected: < 1.69.1

Fixed in: 1.69.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-ban || rpm -q wp-ban || wp-ban --version

2. UPGRADE to 1.69.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-ban

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-ban

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: WordPress WP-Ban <1.69.1 - Stored Cross-Site Scripting

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

wp-ban: upgrade to 1.69.1. Exact commands for each OS are on this page.

Is CVE-2022-4260 being exploited?

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

CVE-2022-4260 affects wp-ban. Severity is medium (CVSS 4.8). The WP-Ban WordPress plugin before 1.69.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is dis

How urgent is CVE-2022-4260?

Priority 36/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-4631 LOW 3.5 MITIGATE A vulnerability, which was classified as problematic, was found in WP-Ban
CVE-2021-4252 LOW 3.5 UPGRADE A vulnerability, which was classified as problematic, has been found in WP-Ban

References

← Back to latest CVEs