CVE-2025-32290
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in LambertGroup Sticky HTML5 Music Player lbg-audio3-html5 allows SQL Injection.This issue affects Sticky HTML5 Music Player: from n/a through <= 3.1.6.
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 confidenceSQL Injection vulnerability in LambertGroup Sticky HTML5 Music Player (lbg-audio3-html5) up to version 3.1.6 allows attackers to inject malicious SQL commands through user-supplied input that is not properly sanitized before being used in database queries.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm LambertGroup Sticky HTML5 Music Player is installedSearch your web server document root for files or directories containing 'lbg-audio3-html5', 'lbg-audio3', or 'sticky-html5-music-player'. Common paths may include /wp-content/plugins/ (if WordPress), /components/, or /media/.Affected if The player files are found in your environment
-
Identify the installed version of lbg-audio3-html5Check for a version file (often named version.php, info.php, or readme.txt) within the player directory. Alternatively, examine the main PHP file header comments for a version declaration. Compare your found version against the affected range: all versions up to and including 3.1.6.Affected if The installed version is 3.1.6 or lower
-
Verify the PHP files handle user input in database queriesExamine the main PHP files (typically lbg-audio3-html5.php or similar) for SQL query execution functions such as mysql_query, mysqli_query, PDO::query, or $wpdb->prepare. Look for occurrences where $_GET, $_POST, or $_REQUEST superglobals are used directly within these queries without visible sanitization functions like esc_sql, htmlspecialchars, or prepared statements.Affected if User-supplied input ($_GET, $_POST, $_REQUEST) flows directly into SQL queries without parameterization or escaping
-
Check if the player admin panel or frontend accepts and stores user inputTest or review the player configuration forms (admin panel) and frontend player parameters (such as playlist IDs, track IDs, or custom fields) to confirm they accept user input and store it in a database. If such inputs exist and reach the SQL queries found in step 3 without sanitization, the flaw is exploitable.Affected if The player accepts user input that gets stored in and retrieved from a database
If lbg-audio3-html5 is installed with version 3.1.6 or lower and any user-provided input reaches database queries without sanitization or prepared statements, the environment is affected by CVE-2025-32290.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation. Apply the latest vendor patch when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-32290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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