CVE-2025-13999
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 · uneditedThe HTML5 Audio Player – The Ultimate No-Code Podcast, MP3 & Audio Player plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions from 2.4.0 up to, and including, 2.5.1 via the getIcyMetadata() function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 confidenceThe WordPress plugin 'HTML5 Audio Player – The Ultimate No-Code Podcast, MP3 & Audio Player' versions 2.4.0-2.5.1 contains a Server-Side Request Forgery (SSRF) vulnerability in the getIcyMetadata() function. This allows unauthenticated attackers to cause the web server to make arbitrary HTTP requests to internal or external resources, potentially exposing sensitive internal services and data.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
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.
-
Locate the plugin installation directoryIn your WordPress wp-content/plugins/ folder, look for a directory named 'html5-audio-player' or similar naming convention related to the HTML5 Audio Player plugin.Affected if The plugin directory exists in the WordPress plugins folder.
-
Identify the installed plugin versionOpen the main plugin file (usually named index.php, main.php, or the plugin PHP file in the plugin root) and look for a version comment or header, or check the readme.txt file for the 'Stable tag' entry.Affected if The version listed is 2.4.0, 2.5.0, 2.5.1, or any version between 2.4.0 and 2.5.1 inclusive.
-
Verify the vulnerable function existsSearch within the plugin directory for the getIcyMetadata() function definition. This function handles metadata retrieval and is where the SSRF flaw exists.Affected if The getIcyMetadata function is found in the plugin code, indicating the vulnerable code is present.
-
Check if the vulnerable endpoint is reachableReview your web server access logs for requests to the WordPress site that may trigger the getIcyMetadata function. The function processes external URLs for audio stream metadata.Affected if External or internal HTTP requests are being made by the plugin without proper URL validation.
You are affected if the HTML5 Audio Player plugin is installed with a version between 2.4.0 and 2.5.1 and the getIcyMetadata function is present and accessible.
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.
dbcve · scopedUpdate the plugin to the latest version which should contain proper URL validation and sanitization in the getIcyMetadata() function to prevent SSRF attacks. If no update is available, consider disabling the plugin until a patched version is released.
2.5.2
- Upgrade the HTML5 Audio Player plugin to version 2.5.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- 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-13999 — 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-13999 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