dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9199

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The Woo superb slideshow transition gallery with random effect plugin for WordPress is vulnerable to SQL Injection via the 'woo-superb-slideshow' shortcode in all versions up to, and including, 9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The Woo superb slideshow transition gallery with random effect WordPress plugin up to version 9.1 contains a SQL Injection vulnerability in the 'woo-superb-slideshow' shortcode handler. The vulnerability stems from insufficient escaping of a user-supplied parameter combined with lack of prepared statements in the underlying SQL query, allowing authenticated attackers with Contributor-level access or higher to inject arbitrary SQL commands.

MitigationUpgrade the plugin to version 9.2 or later. If immediate upgrade is not possible, consider restricting contributor-level shortcode usage or implementing a Web Application Firewall rule to block SQL injection patterns in shortcode parameters.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Woo superb slideshow transition gallery with random effect' or search for 'superb slideshow'. Alternatively, check the plugin directory (wp-content/plugins/) for folders containing 'superb-slideshow' or similar.
    Affected if The plugin folder exists in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins, find the plugin and view the version number under the plugin name. Or check the main plugin file (e.g., woo-superb-slideshow.php) for the 'Version' header comment.
    Affected if Version is 9.1 or lower (versions 9.2 and later contain the fix)
  3. Identify shortcode usage
    Search WordPress content (posts, pages, widgets) for the '[woo-superb-slideshow]' shortcode. This can be done via WordPress admin search, or by querying the wp_posts table: SELECT * FROM wp_posts WHERE post_content LIKE '%[woo-superb-slideshow]%';
    Affected if The shortcode is present in any published content and the plugin version is 9.1 or lower
  4. Confirm contributor-level access exists
    In WordPress admin, go to Users > All Users and review user roles. Check for users with 'Contributor' role or higher (Author, Editor, Administrator). Alternatively, query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%';
    Affected if Any authenticated user with Contributor-level or higher access exists on the site

The environment is affected if the Woo superb slideshow plugin versions 9.1 or lower are installed, the shortcode is in use, and at least one Contributor-level or higher user account exists on the WordPress site.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the plugin to version 9.2 or later. If immediate upgrade is not possible, consider restricting contributor-level shortcode usage or implementing a Web Application Firewall rule to block SQL injection patterns in shortcode parameters.

Recommended fix Moderate confidence

Latest version higher than 9.1 (specific fixed version not specified in advisory)

  1. Check the current version of the 'Woo superb slideshow transition gallery with random effect' plugin in your WordPress installation
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the 'Woo superb slideshow transition gallery with random effect' plugin
  4. If the installed version is 9.1 or lower, update the plugin to the latest available version
Caveat Review plugin changelog for any breaking changes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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