CVE-2025-24587
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Nks Email Subscription Popup email-subscribe allows Blind SQL Injection.This issue affects Email Subscription Popup: from n/a through <= 1.2.23.
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 · high confidenceA blind SQL injection vulnerability exists in the Nks Email Subscription Popup WordPress plugin (versions <= 1.2.23). The email-subscribe functionality fails to properly sanitize user input before using it in SQL queries, allowing attackers to inject malicious SQL commands and potentially extract sensitive data from the database.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify plugin installationNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Nks Email Subscription Popup' in the listAffected if the plugin is installed and active
-
Check installed versionIn the plugins list, locate the version number displayed under the plugin name 'Nks Email Subscription Popup'Affected if the version is 1.2.23 or lower (any version up to and including 1.2.23)
-
Verify plugin statusConfirm whether the plugin is activated - check if the 'Active' status is shown next to the plugin in the WordPress plugins admin pageAffected if the plugin is activated (vulnerability only applies to active instances)
-
Confirm email-subscribe feature exposureCheck if the subscription form or endpoint is publicly accessible - this typically appears as a widget, shortcode, or frontend form that accepts email inputAffected if the email subscription functionality is exposed on the site (the vulnerable code path handles email submissions)
If the Nks Email Subscription Popup plugin is active at version 1.2.23 or lower and the email subscription feature is accessible, the environment is affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpdate to a patched version of the plugin if available. Otherwise, remove the plugin or implement input sanitization and parameterized queries in the vulnerable code paths to remediate the SQL injection.
latest version of Email Subscription Popup plugin (version > 1.2.23)
- 1. Backup your WordPress site before making any changes
- 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
- 3. Locate 'Email Subscription Popup' (Nks Email Subscription Popup)
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. If no update is shown, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
- 6. Verify the updated version number after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24587 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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