VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 3 known issues Latest disclosed Jul 19, 2023

WP Brutal AI Vulnerabilities

Review known vulnerability records for the WordPress plugin WP Brutal AI (`wpbrutalai`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2023-2606, CVE-2023-2601 and CVE-2023-2605, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
3
High or Critical
1
Patch Coverage
100%
Last Updated
Jan 22, 2024
Related Security Guides

Use these guides while reviewing WP Brutal AI fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize WP Brutal AI remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
3
1. Match the Package
Confirm the installed WordPress plugin slug is wpbrutalai before acting on any CVE from this cluster.
2. Sort by Severity
Start with 1 high or critical record, then review medium and unrated findings with public references.
3. Check Patch Evidence
3 records include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2023-2601 High
SQL Injection remediation for WP Brutal AI

Affected range: Versions before 2.0.0. Fixed version: 2.0.0.

CVE-2023-2605 Medium
Cross-Site Scripting remediation for WP Brutal AI

Affected range: Versions before 2.0.1. Fixed version: 2.0.1.

CVE-2023-2606 Medium
Stored Cross-Site Scripting remediation for WP Brutal AI

Affected range: Versions before 2.06. Fixed version: 2.06.

Priority CVE Quick Links

Fast paths into WP Brutal AI CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
3
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2023-2601
WP Brutal AI < 2.0.0 - Cross-Site Request Forgery to SQL Injection
 SQL Injection Versions before 2.0.0 2.0.0 CVSS 8.8
CVE-2023-2605
WP Brutal AI < 2.0.1 - Reflected Cross-Site Scripting
 Cross-Site Scripting Versions before 2.0.1 2.0.1 CVSS 6.1
CVE-2023-2606
WP Brutal AI < 2.06 - Authenticated (Administrator+) Stored Cross-Site Scripting
 Stored Cross-Site Scripting Versions before 2.06 2.06 CVSS 4.4
CVE-2023-2601 High 2.0.0
CVE-2023-2601 WP Brutal AI SQL Injection

WP Brutal AI < 2.0.0 - Cross-Site Request Forgery to SQL Injection

CVE-2023-2605 Medium 2.0.1
CVE-2023-2605 WP Brutal AI Cross-Site Scripting

WP Brutal AI < 2.0.1 - Reflected Cross-Site Scripting

CVE-2023-2606 Medium 2.06
CVE-2023-2606 WP Brutal AI Stored Cross-Site Scripting

WP Brutal AI < 2.06 - Authenticated (Administrator+) Stored Cross-Site Scripting

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for WP Brutal AI so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
3 records include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 1 high severity finding.
Recent CVEs
CVE-2023-2606, CVE-2023-2601 and CVE-2023-2605
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for WP Brutal AI

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2023-2606
CVE-2023-2606: WP Brutal AI < 2.06 - Authenticated (Administrator+) Stored Cross-Site Scripting

The WP Brutal AI plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, but not including, 2.06 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-leve...

Published
Jul 19, 2023
Patched Release
2.06
Affected Versions
Versions before 2.06
Next Step
Update to 2.06 or newer if supported.
Review CVE-2023-2606 fixed version details Open CVE Reference
Plugin High Patched: Yes CVE-2023-2601
CVE-2023-2601: WP Brutal AI < 2.0.0 - Cross-Site Request Forgery to SQL Injection

The WP Brutal AI plugin for WordPress is vulnerable to SQL Injection via an unknown parameter in versions before 2.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. Additionally it lacks a nonce check on...

Published
Jun 05, 2023
Patched Release
2.0.0
Affected Versions
Versions before 2.0.0
Next Step
Update to 2.0.0 or newer if supported.
Review CVE-2023-2601 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2023-2605
CVE-2023-2605: WP Brutal AI < 2.0.1 - Reflected Cross-Site Scripting

The WP Brutal AI plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via admin settings in versions before 2.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pa...

Published
Jun 05, 2023
Patched Release
2.0.1
Affected Versions
Versions before 2.0.1
Next Step
Update to 2.0.1 or newer if supported.
Review CVE-2023-2605 fixed version details Open CVE Reference