Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13999: CWE-918 Server-Side Request Forgery (SSRF) in bplugins HTML5 Audio Player – The Ultimate No-Code Podcast, MP3 & Audio Player

0
High
VulnerabilityCVE-2025-13999cvecve-2025-13999cwe-918
Published: Fri Dec 19 2025 (12/19/2025, 06:48:23 UTC)
Source: CVE Database V5
Vendor/Project: bplugins
Product: HTML5 Audio Player – The Ultimate No-Code Podcast, MP3 & Audio Player

Description

The 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.

AI-Powered Analysis

AILast updated: 12/26/2025, 08:04:28 UTC

Technical Analysis

CVE-2025-13999 is a Server-Side Request Forgery (SSRF) vulnerability identified in the bplugins HTML5 Audio Player – The Ultimate No-Code Podcast, MP3 & Audio Player WordPress plugin, specifically affecting versions from 2.4.0 up to and including 2.5.1. The vulnerability resides in the getIcyMetadata() function, which processes metadata for audio streams. An attacker can exploit this flaw without any authentication or user interaction by crafting requests that cause the server to send arbitrary HTTP requests to internal or external systems. SSRF vulnerabilities allow attackers to bypass network access controls, potentially accessing internal services that are not exposed externally, such as databases, internal APIs, or cloud metadata services. This can lead to information disclosure, unauthorized data modification, or pivoting deeper into the network. The CVSS 3.1 base score of 7.2 reflects the vulnerability's high impact on confidentiality and integrity, with no impact on availability. The vulnerability is notable for its ease of exploitation (no privileges or user interaction required) and the scope of affected systems, given the widespread use of WordPress and this plugin for audio content delivery. While no public exploits are currently known, the vulnerability's publication date in late 2025 suggests that attackers may develop exploits soon, increasing the urgency for mitigation.

Potential Impact

For European organizations, the impact of CVE-2025-13999 can be significant, especially for those relying on WordPress sites that use the vulnerable bplugins HTML5 Audio Player plugin. Exploitation can lead to unauthorized internal network reconnaissance, data leakage from internal services, and potential manipulation of internal resources. This can compromise sensitive corporate data, intellectual property, or customer information. Additionally, SSRF can be a stepping stone for further attacks such as privilege escalation or lateral movement within the network. Organizations in sectors with stringent data protection regulations, such as finance, healthcare, and government, face increased legal and reputational risks if internal data is exposed. The vulnerability's unauthenticated nature means attackers can scan and exploit vulnerable sites at scale, increasing the likelihood of widespread impact across European enterprises and public sector entities.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify the presence of the bplugins HTML5 Audio Player plugin and verify its version. The primary mitigation is to upgrade the plugin to a version beyond 2.5.1 once a patch is released by the vendor. Until a patch is available, organizations should consider disabling or removing the plugin to eliminate the attack surface. Web application firewalls (WAFs) can be configured to detect and block suspicious requests targeting the getIcyMetadata() function or unusual outbound HTTP requests originating from the web server. Network segmentation should be enforced to restrict the web server's ability to access internal services unnecessarily. Additionally, internal services should implement strict access controls and authentication to prevent unauthorized access even if SSRF occurs. Monitoring and logging outbound requests from web servers can help detect exploitation attempts early. Finally, organizations should educate their security teams about SSRF risks and incorporate SSRF testing into regular security assessments.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-03T23:11:51.326Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6944f80919341fe18889df14

Added to database: 12/19/2025, 7:00:25 AM

Last enriched: 12/26/2025, 8:04:28 AM

Last updated: 2/8/2026, 2:21:29 AM

Views: 77

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats