CVE-2024-43319

Flash & HTML5 Video <= 2.5.31 - Authenticated (Subscriber+) Information Exposure

2024-08-16 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 2.5.32
Affected Version
<= 2.5.31
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-43319
View all HTML5 Video Player – embed fast, responsive videos with ease vulnerabilities

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

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C