dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30947

HIGH · 8.5 CVSS v3.1 Published 2025-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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 gopiplus Cool fade popup cool-fade-popup allows Blind SQL Injection.This issue affects Cool fade popup: from n/a through <= 10.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

The Cool fade popup WordPress plugin versions through 10.1 contains a blind SQL injection vulnerability. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through insufficient input sanitization in the plugin's parameters. This high-severity (CVSS 8.5) issue can lead to extraction of sensitive data from the database via time-based or boolean-based blind SQL injection techniques.

MitigationUpdate the Cool fade popup plugin to the latest version as soon as a patch is released. If no patch is available, consider disabling the plugin until a secure version can be deployed, as SQL injection can compromise the entire WordPress 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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Cool fade popup. The version number is displayed below the plugin name. Alternatively, check the plugin header in its main PHP file or the readme.txt file in the plugin directory.
    Affected if Version is 10.1 or lower (versions through 10.1 are affected)
  2. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins. Confirm whether Cool fade popup shows as Active. The vulnerability is exploitable only when the plugin is enabled.
    Affected if Plugin is currently active and enabled on the site
  3. Confirm public accessibility
    Visit pages on the site where the popup shortcode or widget may be displayed, or check the plugin settings for any frontend visibility options. The vulnerability is exploitable by unauthenticated attackers via HTTP requests.
    Affected if Plugin functionality is exposed to unauthenticated visitors

You are affected if the Cool fade popup plugin version is 10.1 or lower and the plugin is active and publicly accessible.

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

Update the Cool fade popup plugin to the latest version as soon as a patch is released. If no patch is available, consider disabling the plugin until a secure version can be deployed, as SQL injection can compromise the entire WordPress database.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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