CVE-2025-32306
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 Radio Player Shoutcast & Icecast WordPress Plugin audio4-html5 allows Blind SQL Injection.This issue affects Radio Player Shoutcast & Icecast WordPress Plugin: from n/a through <= 4.4.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 confidenceA blind SQL injection vulnerability exists in the LambertGroup Radio Player Shoutcast & Icecast WordPress Plugin (audio4-html5) due to improper neutralization of special elements in SQL commands. Attackers can inject malicious SQL queries through vulnerable parameters to extract data from the database or cause denial of service.
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 the plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'audio4-html5', 'radio-player-shoutcast-icecast', or 'lambertgroup-radio-player'. Alternatively, view the installed plugins list in the WordPress admin dashboard.Affected if The plugin folder or listing is present in the WordPress installation.
-
Determine the installed plugin versionIf the plugin is installed, locate its main PHP file (usually in the plugin folder root) and search for a version definition comment or a 'Version:' header in the plugin metadata. In WordPress admin, go to Plugins > Installed Plugins and look for the version number next to the plugin name.Affected if The version displayed cannot be confirmed as patched or is within an unknown vulnerable range.
-
Inspect for vulnerable parameter exposureReview the plugin's PHP files for any $_GET, $_POST, or $_REQUEST parameters being used directly in SQL queries without proper escaping, prepared statements, or parameter binding. Focus on files that handle user input related to radio streams, playlist loading, or shoutcast/icecast connections.Affected if Direct use of unsanitized request parameters in SQL queries is found in the plugin code.
-
Examine web application logs for SQL injection attemptsReview Apache/Nginx access logs and WordPress debug logs for unusual SQL syntax patterns in URLs or POST data targeting the plugin's PHP files. Look for patterns like 'UNION SELECT', 'OR 1=1', or sleep() functions.Affected if Evidence of SQL injection attempts against the plugin endpoints exists in the logs.
A defender is affected if the LambertGroup Radio Player plugin is installed and the installed version is not confirmed as patched or if suspicious SQL-like patterns appear in logs targeting the plugin.
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 dataUpdate the plugin to the latest version immediately. If no patched version is available, disable or remove the plugin. Consider deploying a WAF rule as a temporary compensating control.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32306 — 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-32306 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