dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22540

CRITICAL · 9.3 CVSS v3.1 Published 2025-01-09
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in seballero Emailing Subscription email-suscripcion allows Blind SQL Injection.This issue affects Emailing Subscription: from n/a through <= 1.4.1.

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

A blind SQL injection vulnerability exists in seballero's Emailing Subscription plugin (email-suscripcion) up to version 1.4.1. The vulnerability stems from improper neutralization of special elements in SQL commands, allowing attackers to inject malicious SQL queries through unsanitized user input. The 'blind' classification indicates the attacker may not see direct database output but can infer results through application behavior differences.

MitigationUpgrade to a patched version of the Emailing Subscription plugin; if no patch exists, refactor vulnerable code to use parameterized queries or prepared statements with proper input validation on all database interactions.

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. Locate the Emailing Subscription plugin
    Check your WordPress installation under wp-content/plugins/ for a folder named 'email-suscripcion' or similar variant. Alternatively, access the Plugins section in WordPress admin and look for 'Emailing Subscription' or 'Email Suscripcion' in the installed plugins list.
    Affected if The plugin is present in the installation
  2. Determine the installed version
    If found in the WordPress admin Plugins page, view the plugin details to see the version number. Alternatively, open the main plugin PHP file (usually email-suscripcion.php or similar) and look for the 'Version:' header in the plugin comment block at the top of the file.
    Affected if The reported version is 1.4.1 or any lower version number
  3. Verify the plugin handles user input in database queries
    Examine the plugin PHP files for SQL query code. Look for database interaction functions (such as $wpdb->prepare, $wpdb->query, mysql_query, mysqli_query, or similar) and check if any user-supplied data (from $_GET, $_POST, $_REQUEST, or function parameters) is concatenated directly into SQL strings without using parameterized queries or input sanitization functions.
    Affected if User input from HTTP requests appears in raw SQL queries without prepared statements or sanitization functions such as esc_sql() or sanitize_text_field()
  4. Identify if blind SQL injection is exploitable
    Test the plugin's public-facing forms (typically subscription/unsubscription forms) by submitting SQL meta-characters in form fields (such as a single quote ' or boolean-based payloads like ' OR '1'='1) and observe whether the application exhibits different behavior (error messages, delayed responses, or altered page content) that suggests the input is being interpreted as SQL rather than treated as literal data.
    Affected if The application responds differently to SQL meta-characters in form inputs, indicating unsanitized input is being passed to the database

You are affected if the Emailing Subscription plugin version is 1.4.1 or lower AND the plugin code contains direct SQL queries using unsanitized user input from HTTP parameters.

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 patched version of the Emailing Subscription plugin; if no patch exists, refactor vulnerable code to use parameterized queries or prepared statements with proper input validation on all database interactions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22540 — 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-2025-22540 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