dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39530

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated SQL Injection in SpeakOut! Email Petitions <= 4.6.5 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unauthenticated SQL Injection vulnerability in SpeakOut! Email Petitions WordPress plugin version 4.6.5 and earlier, allowing remote attackers to inject malicious SQL queries without authentication.

MitigationUpgrade to a version newer than 4.6.5; if no patched version is available, disable the plugin immediately and implement web application firewall rules to block SQL injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if SpeakOut! Email Petitions plugin is installed
    Navigate to WordPress admin > Plugins, or inspect /wp-content/plugins/ directory for 'speakout' or 'email-petitions' folder
    Affected if Plugin folder exists in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > SpeakOut! Email Petitions and read the version number from the plugin description, or check the 'readme.txt' or 'speakout.php' file header in the plugin folder
    Affected if Version is 4.6.5 or any earlier version
  3. Verify the plugin is active and accessible
    Check WordPress admin > Plugins to confirm the plugin status shows 'Active', and verify the plugin public-facing functionality is not disabled via plugin settings
    Affected if Plugin is active and its petition forms are publicly accessible
  4. Confirm exposure to unauthenticated requests
    Inspect WordPress settings for any access controls or membership restrictions on the plugin's shortcode [emailpetition] or its submit endpoint; verify the site allows public (non-logged-in) access to petition form pages
    Affected if Petition forms are publicly accessible without authentication

If SpeakOut! Email Petitions plugin version 4.6.5 or earlier is installed and active with publicly accessible petition forms, the environment is affected by this unauthenticated SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version newer than 4.6.5; if no patched version is available, disable the plugin immediately and implement web application firewall rules to block SQL injection attempts.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39530 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data