CVE-2025-31926
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 Radio Player lbg-audio5-html5-shoutcast_sticky allows SQL Injection.This issue affects Sticky Radio Player: from n/a through <= 3.4.
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 · moderate confidenceSQL Injection vulnerability in LambertGroup Sticky Radio Player (lbg-audio5-html5-shoutcast_sticky) allows attackers to inject malicious SQL commands via unsanitized user inputs. The flaw affects versions through 3.4 and could enable unauthorized database access or data exfiltration.
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.
-
Identify if LambertGroup Sticky Radio Player is installedSearch for files or directories containing 'lbg-audio5-html5-shoutcast_sticky' or 'sticky-radio-player' in the web root or application directoriesAffected if The LambertGroup Sticky Radio Player is present on the system
-
Determine the installed version of the playerCheck version files, readme files, or examine the main script file (often named version.php, info.php, or similar) for a version stringAffected if The installed version is 3.4 or any earlier version (versions through 3.4 are affected)
-
Locate database interaction scriptsSearch for PHP or other server-side files in the player directory that contain SQL query functions (mysql_query, mysqli_query, PDO query, sqlite_query, etc.)Affected if Database interaction scripts exist and the player uses a database
-
Identify user input in SQL queriesExamine the database scripts for direct insertion of $_GET, $_POST, or $_REQUEST parameters into SQL statements without visible sanitization functions (such as mysqli_real_escape_string, htmlspecialchars, parameterized queries)Affected if User-supplied input parameters are concatenated directly into SQL queries without sanitization or parameterization
-
Verify database configuration exposureCheck for exposed database configuration files (config.php, db.php, or similar) that may contain credentials accessible to an attacker if SQL injection is exploitedAffected if Database credentials are stored in files accessible via the web and could be retrieved through successful SQL injection
The environment is affected if the LambertGroup Sticky Radio Player version 3.4 or earlier is installed and contains database interaction code that directly incorporates user input into SQL queries without sanitization.
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 dataImplement parameterized queries or prepared statements for all database interactions. Audit and sanitize all user-supplied inputs before using them in SQL queries. Consider updating to a patched version if available from the vendor.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31926 — 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-31926 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