dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30806

HIGH · 8.5 CVSS v3.1 Published 2025-03-27
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 Constantin Boiangiu Vimeotheque codeflavors-vimeo-video-post-lite allows SQL Injection.This issue affects Vimeotheque: from n/a through <= 2.3.4.2.

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 Vimeotheque WordPress plugin (codeflavors-vimeo-video-post-lite) allows attackers to inject malicious SQL commands via unsanitized user input. The vulnerability affects all versions through 2.3.4.2 and could allow unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate Vimeotheque to the latest patched version immediately. If no patch is available, disable the plugin, implement a WAF rule to filter SQL injection attempts, and/or add parameterized queries/input sanitization to the affected code paths.

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 Vimeotheque plugin version
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, locate Vimeotheque (codeflavors-vimeo-video-post-lite), and read the version number displayed below the plugin name. Alternatively, open wp-content/plugins/codeflavors-vimeo-video-post-lite/vimeotheque.php and find the Version: header in the plugin comments.
    Affected if the installed version is 2.3.4.2 or any earlier version (all versions through 2.3.4.2 are affected)
  2. Confirm Vimeotheque plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that Vimeotheque shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if the plugin is active and running, as only active installations process the vulnerable code paths
  3. Inspect plugin for unsanitized SQL query functions
    Access the plugin files via FTP or file manager. Search the codebase for direct SQL query patterns: look for $wpdb->prepare(), $wpdb->query(), or $wpdb->get_results() calls and verify that any user-supplied input ($_GET, $_POST, $_REQUEST) passed to these functions is properly escaped or parameterized. Also check for any raw query concatenation using variables from request parameters.
    Affected if you find SQL queries that use $_GET, $_POST, or $_REQUEST variables without using $wpdb->prepare() or equivalent sanitization functions
  4. Review WordPress debug logs for SQL errors
    If WordPress debug logging is enabled (wp-config.php contains define('WP_DEBUG', true)), check wp-content/debug.log for SQL syntax errors or warnings that may indicate exploitation attempts. Also review your web server access logs for unusual query patterns targeting Vimeotheque endpoints.
    Affected if you see SQL error messages in logs containing Vimeotheque URL paths, or suspicious query strings with SQL keywords (UNION, SELECT, INSERT, etc.) in your access logs

You are affected if the Vimeotheque plugin version is 2.3.4.2 or earlier AND the plugin is active, since all versions through 2.3.4.2 contain the 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

Update Vimeotheque to the latest patched version immediately. If no patch is available, disable the plugin, implement a WAF rule to filter SQL injection attempts, and/or add parameterized queries/input sanitization to the affected code paths.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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