Skip to main content

AIWU Plugin EUVDEUVD-2026-43429

| CVE-2026-59515 CRITICAL
SQL Injection (CWE-89)
2026-07-13 Patchstack
9.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running AIWU plugin
  2. Delivery
    Send crafted request to vulnerable parameter
  3. Exploit
    Inject blind SQL payload
  4. Execution
    Infer data via boolean/timing responses
  5. Impact
    Extract credentials and secrets from database

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The target must be a WordPress site running the AIWU ai-copilot-content-generator plugin at version 1.5.4 or earlier, with the vulnerable plugin request handler reachable over the network. Per the provided CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication or user interaction is required against a default installation, which maximizes exposure; the primary limiting factor is simply having the plugin installed and active. Caveat: Patchstack plugin SQLi entries frequently do require a low-privileged authenticated session despite a PR:N score, so defenders should confirm from the Patchstack advisory whether any account (e.g., subscriber) is actually needed, as that materially changes real-world exploitability.

Impact

The supplied CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L, base 9.3) describes an unauthenticated, network-reachable, low-complexity attack with changed scope and high confidentiality impact - signals that justify a Critical rating. However, EPSS is not provided, there is no KEV listing, and no POC is referenced, so no evidence of active or automated exploitation exists yet; the score reflects potential rather than observed abuse. A meaningful caveat: many WordPress plugin SQLi issues catalogued by Patchstack actually require at least low-level authentication (subscriber/contributor), yet this vector asserts PR:N - this should be verified against the Patchstack advisory, because if some privilege is in fact required the real-world exposure is lower than the raw 9.3 suggests. Treat as a high-priority patch/mitigation target for any internet-facing site running this plugin, while confirming the true authentication prerequisite.

Exploit ScenarioDerived

An attacker sends crafted HTTP requests to the vulnerable AIWU plugin endpoint on a public WordPress site, embedding blind SQL injection payloads (boolean or time-based) into an unsanitized parameter. By observing response differences or induced delays, the attacker iteratively extracts wp_users password hashes and secret keys from the database, then cracks or reuses them to escalate access. No public POC is referenced, but the low attack complexity makes weaponization straightforward for a skilled actor.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 13, 2026

Blind SQL injection in the Sergey "AIWU" ai-copilot-content-generator WordPress plugin (all versions through 1.5.4) allows remote attackers to inject arbitrary SQL into backend database queries, per the CVSS:3.1 vector without requiring authentication or user interaction. Because the scope is changed and confidentiality impact is High, an attacker can exfiltrate sensitive database contents (WordPress user credentials, secrets, PII) via time- or boolean-based blind techniques. No public exploit identified at time of analysis and the issue is not on CISA KEV, but its high CVSS (9.3) and the fact that it was catalogued by Patchstack make it a credible risk for exposed WordPress sites.

RemediationAI

No vendor-released patch version is identified at time of analysis, so no exact upgrade target can be cited from the input; monitor the Patchstack advisory (https://patchstack.com/database/Wordpress/Plugin/ai-copilot-content-generator/vulnerability/wordpress-aiwu-plugin-1-5-4-sql-injection-vulnerability) and the WordPress.org plugin page for a release above 1.5.4 and apply it immediately when available. Until then, the safest compensating control is to deactivate and remove the ai-copilot-content-generator plugin, accepting loss of its AI content-generation feature. If removal is not acceptable, deploy a WordPress-aware WAF (such as Patchstack's own virtual patching) or restrict/authenticate access to the plugin's request endpoints via web-server rules, and consider blocking the affected AJAX/REST routes at the reverse proxy - noting this may break legitimate plugin functionality. As defense in depth, apply least-privilege to the database account used by WordPress to limit what a successful injection can read.

Affected VersionsENISA

AIWU 0 ≤1.5.4

Affected Packages

euvd aiwu no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin (cpe:2.3:a:sergey:aiwu:*) that adds AI-assisted content generation to WordPress. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), meaning user-controllable input is concatenated into a SQL statement executed against the WordPress MySQL/MariaDB database without proper parameterization or escaping (e.g., missing use of $wpdb->prepare()). The "Blind" qualifier indicates the query results are not returned directly in the HTTP response, so an attacker infers data by observing behavioral or timing differences - a slower but fully effective extraction method. Patchstack, a WordPress-focused vulnerability intelligence vendor, is the reporting source.

Know when Aiwu gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 6.5 MEDIUM

Network SQLi with low complexity; PR:L reflects the typical low-privilege auth for Patchstack plugin SQLi, scope unchanged, high confidentiality read but no integrity/availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:N/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Sergey AIWU ai-copilot-content-generator allows Blind SQL Injection.This issue affects AIWU: from n/a through <= 1.5.4.

Executive ViewAI

Why It Matters

The ai-copilot-content-generator WordPress plugin (all versions through 1.5.4) contains a critical blind SQL injection vulnerability (CVE-2026-59515, CVSS 9.3) that allows unauthenticated attackers to exfiltrate WordPress administrator credentials, database secrets, and customer PII without user interaction. Any organization running this plugin on publicly accessible WordPress sites faces immediate risk of credential compromise and unauthorized database access, with no public exploit identified at time of analysis but high credibility given the vulnerability's severity and documentation by Patchstack.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: implement Web Application Firewall blocking SQL injection patterns; restrict WordPress database user permissions to minimum required privileges; enable database query logging with real-time monitoring for anomalies; apply IP-based rate limiting on WordPress login endpoints; isolate WordPress environments through network segmentation; consider taking the site offline until the plugin is replaced with a secure alternative.

Threat Intelligence Overview

EPSS Score
0.4%
Top 68% exploitable
Prevalence
Rare
obscure niche WordPress AI-content plugin, minimal deployment footprint
Social Media
3
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy