CVE-2023-2601: The wpbrutalai WordPress plugin before 2.0.0 does not properly sanitise and escape a parameter before using it

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

wp brutal ai: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-2601 being exploited?

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

CVE-2023-2601 affects wp brutal ai. Severity is critical (CVSS 9.8). The wpbrutalai WordPress plugin before 2.0.0 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by admin via CSRF.

Q: How urgent is CVE-2023-2601?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2023-2601 is a critical-severity flaw (CVSS 9.8) affecting wp brutal ai. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The wpbrutalai WordPress plugin before 2.0.0 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by admin via CSRF.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 22%)
CISA exploited list	No
Published	2023-06-27
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp brutal ai project

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

Am I affected?

Timeline

2023-06-27 14:15 UTCPublished CVE record published
2026-06-17 05:52 UTCUpdated Record last modified

wp brutal ai project wp brutal ai UPGRADE

Affected: < 2.0.0

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-brutal-ai || rpm -q wp-brutal-ai || wp-brutal-ai --version

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-brutal-ai

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-brutal-ai

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

wp brutal ai: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2023-2601 being exploited?

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

CVE-2023-2601 affects wp brutal ai. Severity is critical (CVSS 9.8). The wpbrutalai WordPress plugin before 2.0.0 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by admin via CSRF.

How urgent is CVE-2023-2601?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-2606 MEDIUM 4.8 UPGRADE The WP Brutal AI WordPress plugin before 2.06 does not sanitise and escape some of its settings, which could a
CVE-2023-2605 MEDIUM 6.1 UPGRADE The wpbrutalai WordPress plugin before 2.0.1 does not sanitise and escape a parameter before outputting it bac

References

← Back to latest CVEs