CVE-2025-13999
Server-Side Request Forgery in HTML5 Audio Player Plugin
Publication date: 2025-12-19
Last updated on: 2025-12-19
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | html5_audio_player | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Server-Side Request Forgery (SSRF) in the HTML5 Audio Player WordPress plugin versions 2.4.0 through 2.5.1. It occurs via the getIcyMetadata() function, allowing unauthenticated attackers to make web requests from the web application to arbitrary locations. This can be exploited to query and modify information from internal services that are otherwise inaccessible.
How can this vulnerability impact me? :
The vulnerability can allow attackers to make unauthorized requests from the vulnerable web application to internal or external systems. This can lead to unauthorized access or modification of internal service data, potentially exposing sensitive information or enabling further attacks within the internal network.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve monitoring for unauthorized or unusual HTTP POST requests to the vulnerable WordPress plugin's AJAX endpoint that invoke the getIcyMetadata() function or related stream data retrieval functions. Look for POST requests containing parameters like 'nonce' and 'url' targeting the html5-audio-player plugin. Network traffic inspection tools such as tcpdump or Wireshark can be used to capture such requests. For example, a command to capture HTTP POST requests to the plugin's AJAX endpoint might be: tcpdump -i any -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'POST.*html5-audio-player'. Additionally, reviewing web server logs for suspicious POST requests with unusual or external URLs in the 'url' parameter can help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the HTML5 Audio Player WordPress plugin to version 2.5.2 or later, which contains the patch for CVE-2025-13999. The patch improves nonce verification by tightening the security context, enforces domain whitelisting for stream URLs to prevent unauthorized requests, and sanitizes input properly. If updating immediately is not possible, consider disabling the plugin or restricting access to its AJAX endpoints to trusted users only. Additionally, review and configure the whitelist of allowed stream URLs to limit potential abuse. [2]