Html5 Audio Player <= 2.1.2 - Contributor+ Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1.3
- Affected Version
<= 2.1.2- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24412
At a glance
CVE-2021-24412 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the HTML5 Audio Player WordPress plugin, affecting versions <= 2.1.2. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.1.3; sites on affected versions should update now. Disclosed September 2021, reported by Michal Lipinski.
Vulnerability Overview
The Html5 Audio Player – Audio Player for WordPress plugin before 2.1.3 does not sanitise or validate the parameters from its shortcode, allowing users with a role as low as contributor to set Cross-Site Scripting payload in them which will be triggered in the page/s with the embed malicious shortcode
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in HTML5 Audio Player <= 2.1.2 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For HTML5 Audio Player the fix is 2.1.3: builds <= 2.1.2 are affected, anything from 2.1.3 onward is not.
Remediation
Update to version 2.1.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to HTML5 Audio Player: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: HTML5 Audio Player 2.1.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in HTML5 Audio Player – The Ultimate No-Code Podcast, MP3 & Audio Player
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C