dbcve.org
Html5 Audio PlayerWordPress extension · Bplugins

CVE-2024-37445

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 2.2.24 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in bPlugins Html5 Audio Player allows Stored XSS.This issue affects Html5 Audio Player: from n/a through 2.2.23.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored XSS vulnerability in bPlugins Html5 Audio Player allows attackers to inject malicious JavaScript code through unsanitized input fields. The improper neutralization of input during web page generation means the malicious payload is stored in the database and executed when other users access the affected pages.

MitigationUpdate Html5 Audio Player to the latest version after patches are released. Until then, restrict access to the plugin's admin interfaces and validate/sanitize all user inputs using WordPress sanitization functions like sanitize_text_field(), esc_html(), and esc_attr() before output.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Html5 Audio PlayerWordPress extension
Affected:< 2.2.24

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the Html5 Audio Player plugin is installed
    Check the WordPress plugin directory (wp-content/plugins/html5-audio-player) or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    Locate the main plugin file (index.php or html5-audio-player.php) and read the Version header in the plugin comments, or check via WP-CLI: wp plugin list --name=html5-audio-player
    Affected if The version number is lower than 2.2.24
  3. Verify admin access to plugin settings
    Log into WordPress admin panel and navigate to the plugin settings page (usually under Settings or the plugin's own menu item in the left sidebar)
    Affected if The plugin admin interface is accessible and allows input (the vulnerability exists in unsanitized input fields here)
  4. Inspect stored data for potential malicious scripts
    Check the WordPress database tables where plugin data is stored (typically wp_options or a custom table created by the plugin) for unsanitized user input that may contain script tags
    Affected if Stored data contains unescaped HTML or JavaScript content that could execute

A user is affected if the Html5 Audio Player plugin versions below 2.2.24 are installed and the admin interface with input fields is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.24 or later
Fixed in 2.2.24
Interim mitigation

Update Html5 Audio Player to the latest version after patches are released. Until then, restrict access to the plugin's admin interfaces and validate/sanitize all user inputs using WordPress sanitization functions like sanitize_text_field(), esc_html(), and esc_attr() before output.

Recommended fix High confidence

2.2.24

  1. 1. Create a full backup of your WordPress site before updating the plugin
  2. 2. Navigate to WordPress admin dashboard > Plugins > Html5 Audio Player
  3. 3. Click 'Update Now' to update to version 2.2.24, or manually download version 2.2.24 from the WordPress plugin repository and upload it
  4. 4. After updating, clear any caching plugins if present
  5. 5. Verify the plugin is running version 2.2.24 under Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Html5 Audio Player Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37445 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data