Skip to main content
CVE-2025-13999VulnerabilityPublished

CVE-2025-13999: HTML5 Audio Player (WordPress plugin) · Server-Side Request Forgery (SSRF)

Affects HTML5 Audio Player (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
bplugins HTML5 Audio Player – The Ultimate No-Code Podcast, MP3 & Audio PlayerAffected
  • =2.4.0
Fixed in–

AI-suggested

To mitigate CVE-2025-13999, organizations should immediately assess their WordPress installations for the presence of the vulnerable bplugins HTML5 Audio Player plugin versions 2.4.0 through 2.5.1. If found, the plugin should be disabled or removed until a vendor patch is released. Network-level controls should be implemented to restrict outbound HTTP requests from the web server hosting WordPress, limiting them to only necessary destinations to reduce SSRF attack surface. Web Application Firewalls (WAFs) can be configured to detect and block suspicious requests targeting the getIcyMetadata() function or unusual request patterns indicative of SSRF attempts. Administrators should monitor logs for anomalous outbound connections and unusual internal service access. If patching is delayed, consider isolating the WordPress server in a segmented network zone with minimal access to internal resources. Additionally, review and harden internal services to require strong authentication and avoid trusting requests originating from the WordPress server. Regularly update all plugins and themes to the latest versions and subscribe to vulnerability advisories from the plugin vendor and WordPress security sources. Employing runtime application self-protection (RASP) solutions can also help detect and block SSRF exploitation attempts in real time.

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.

References

Community reviews

Loading reviews…