dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30589

HIGH · 8.5 CVSS v3.1 Published 2025-04-01
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 Dourou Flickr set slideshows flickr-set-slideshows allows SQL Injection.This issue affects Flickr set slideshows: from n/a through <= 0.9.

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 confidence

SQL injection vulnerability in the Dourou Flickr set slideshows WordPress plugin (version <= 0.9) allows attackers to inject malicious SQL commands through unsanitized input in the flickr-set-slideshows functionality, potentially enabling data exfiltration or database compromise.

MitigationUpgrade to a patched version of the plugin that implements parameterized queries or proper input sanitization; if no patch exists, disable the plugin until a secure version is available.

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. Verify flickr-set-slideshows plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the flickr-set-slideshows folder, or list installed plugins via wp-cli: wp plugin list --name=flickr-set-slideshows
    Affected if The flickr-set-slideshows folder exists in the plugins directory
  2. Determine installed plugin version
    Read the plugin header from flickr-set-slideshows.php to find the Version field, or run: wp plugin get flickr-set-slideshows --field=version
    Affected if The installed version is 0.9 or lower (all versions up to 0.9 are affected)
  3. Check if plugin is active
    Query the WordPress options table for the active_plugins option, or run: wp plugin is-active flickr-set-slideshows
    Affected if The plugin is active and accessible to users
  4. Identify the vulnerable input point
    Review plugin source code for SQL queries that use unsanitized user-supplied input (look for direct $_GET, $_POST, or $_REQUEST usage in database queries without prepare() or sanitization functions)
    Affected if The plugin processes user input through SQL queries without parameterized queries or input sanitization

If the flickr-set-slideshows plugin is installed and active at version 0.9 or below, the environment is affected by this 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 patched version of the plugin that implements parameterized queries or proper input sanitization; if no patch exists, disable the plugin until a secure version is available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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