Flash & HTML5 Video <= 2.5.31 - Authenticated (Subscriber+) Information Exposure
Strategic Overview
- Status
- Patched in 2.5.32
- Affected Plugin
- HTML5 Video Player – embed fast, responsive videos with ease
- Affected Version
<= 2.5.31- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-43319
At a glance
CVE-2024-43319 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the HTML5 Video Player WordPress plugin, affecting versions <= 2.5.31. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.5.32; sites on affected versions should update now. Disclosed August 2024, reported by Ananda Dhakal.
Vulnerability Overview
The HTML5 Video Player – mp4 Video Player Plugin and Block plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.5.31 via the h5vp_export_data() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract potentially sensitive information from exports.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
HTML5 Video Player <= 2.5.31 carries this weakness at h5vp_export_data(), and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For HTML5 Video Player the fix is 2.5.32: builds <= 2.5.31 are affected, anything from 2.5.32 onward is not.
Remediation
Update to version 2.5.32, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: HTML5 Video Player 2.5.32 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in HTML5 Video Player – embed fast, responsive videos with ease
- 10.0CVE-2024-5522: HTML5 Video Player <= 2.5.26 SQL Injection
CVE-2024-5522 - 6.5CVE-2024-1061: HTML5 Video Player <= 2.5.24 SQL Injection
CVE-2024-1061 - 6.4CVE-2024-13156: HTML5 Video Player DOM-Based Stored XSS
CVE-2024-13156 - 6.4CVE-2024-43296: Flash & HTML5 Video <= 2.5.30 Missing Authorization
CVE-2024-43296 - 6.4CVE-2023-6485: Html5 Video Player <= 2.5.18 Stored XSS
CVE-2023-6485 - 5.3CVE-2026-57323: HTML5 Video Player Missing Authorization
CVE-2026-57323 - 5.3CVE-2024-7727: HTML5 Video Player Missing Authorization in multiple
CVE-2024-7727 - 4.3CVE-2024-7721: HTML5 Video Player Authenticated (Subscriber+) Limited
CVE-2024-7721
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C