dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47567

HIGH · 7.6 CVSS v3.1 Published 2025-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 LambertGroup Video Player & FullScreen Video Background universal-video-player-and-bg allows Blind SQL Injection.This issue affects Video Player & FullScreen Video Background: from n/a through <= 2.4.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 · high confidence

A blind SQL injection vulnerability exists in the LambertGroup universal-video-player-and-bg plugin (versions up to 2.4.1). Attackers can inject malicious SQL queries through unsanitized input parameters, potentially exfiltrating data from the database via blind injection techniques. The high CVSS score (7.6) reflects the potential for complete confidentiality compromise.

MitigationReplace all dynamic SQL queries with parameterized queries or prepared statements, implement strict input validation, and apply the principle of least privilege to database accounts. Upgrade to a patched version if 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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Locate the LambertGroup universal-video-player-and-bg plugin in your CMS/plugin directory (typically /wp-content/plugins/ for WordPress) or check your plugin management interface
    Affected if The plugin is present in the installation
  2. Identify installed version
    Open the main plugin file (often named index.php, main.php, or plugin-name.php) and locate the version declaration in the plugin header comment or version constant
    Affected if The installed version is 2.4.1 or any lower version (the vendor notes versions up to 2.4.1 are affected)
  3. Verify input handling exists
    Search plugin source code for dynamic SQL query construction using variables that could contain user input (look for patterns like $wpdb->prepare with concatenated variables, direct query execution with $_GET, $_POST, or $_REQUEST parameters)
    Affected if The plugin contains SQL queries that accept user-supplied input without proper sanitization or parameterization
  4. Check for vulnerable parameter exposure
    Review the plugin's admin panels, frontend shortcodes, or AJAX endpoints to identify which URL parameters or form inputs are passed to database queries
    Affected if User-accessible parameters (via URL query strings, POST data, or cookies) are used in SQL queries without prepared statements
  5. Inspect database user privileges
    Examine the database user credentials configured in the plugin's database connection (wp-config.php for WordPress or config files for other platforms) to determine if the application database user has unnecessary privileges beyond SELECT, INSERT, UPDATE, DELETE
    Affected if The database user has elevated privileges (such as DROP, CREATE, or file permissions) which could amplify the impact of SQL injection

You are affected if the LambertGroup universal-video-player-and-bg plugin versions 2.4.1 or lower is installed and user-controlled input reaches unsanitized SQL query execution points in the plugin code

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

Replace all dynamic SQL queries with parameterized queries or prepared statements, implement strict input validation, and apply the principle of least privilege to database accounts. Upgrade to a patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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