Summary
CVE-2026-39530 is a critical unauthenticated SQL injection vulnerability (CWE-89) affecting the SpeakOut! Email Petitions WordPress plugin in all versions up to and including 4.6.5. With a CVSS v3.1 score of 9.3 (Critical), the flaw allows any unauthenticated remote attacker to interact directly with the underlying WordPress database, enabling the exfiltration of sensitive data including user credentials and petition signer PII. The plugin vendor has released version 4.6.5.1 as a critical security patch, and immediate updating is strongly recommended.
Technical details
- Root cause: Improper neutralization of special elements used in SQL commands (CWE-89); the plugin fails to adequately sanitize user-supplied input before incorporating it into database queries.
- Attack method: Blind SQL injection (CAPEC-7) — attackers craft time-based or boolean-based payloads to systematically extract data from the database without triggering visible error output.
- Attack vector: Exploitable remotely over the network (AV:N) with no authentication required (PR:N) and no user interaction (UI:N), meaning any anonymous internet user can trigger the injection.
- Impact: High confidentiality impact (C:H) with Changed Scope (S:C) — successful exploitation enables full read access to the WordPress database, including user credentials, petition signer personally identifiable information (PII), and other sensitive site data. A low availability impact (A:L) is also present.
Affected software
- SpeakOut! Email Petitions WordPress Plugin, versions <= 4.6.5
Severity
- CVSS v3.1 Base Score: 9.3 (Critical)
- Vector string:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Mitigation and recommended actions
- Immediate action: Update the SpeakOut! Email Petitions plugin to version 4.6.5.1 or later. The plugin author explicitly describes 4.6.5.1 as a "critical security patch" and urges users to "update immediately to protect your user data."
- If immediate patching is not possible: Temporarily disable the SpeakOut! Email Petitions plugin, or apply network-level controls restricting access to the WordPress AJAX endpoint, until the patch can be applied.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

