dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-10816

HIGH · 7.5 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The LUNA RADIO PLAYER plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 6.24.01.24 via the js/fallback.php file. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

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 · high confidence

The LUNA RADIO PLAYER WordPress plugin is vulnerable to directory traversal via the js/fallback.php file in all versions up to 6.24.01.24. This allows unauthenticated attackers to read arbitrary files on the server by manipulating path parameters in the fallback.php script, potentially exposing sensitive configuration files, credentials, or other system files.

MitigationUpdate the LUNA RADIO PLAYER plugin to a version newer than 6.24.01.24 immediately. If no patched version is available, disable and remove the plugin until a fix is released. Alternatively, restrict access to the js/fallback.php file via web server configuration.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Locate the LUNA RADIO PLAYER plugin directory
    Check if the wp-content/plugins/luna-radio-player directory exists on the server filesystem
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open wp-content/plugins/luna-radio-player/readme.txt and look for the 'Stable tag:' line, or check the main plugin PHP file header for 'Version:'
    Affected if The version is 6.24.01.24 or lower
  3. Verify fallback.php exists
    Check if the file wp-content/plugins/luna-radio-player/js/fallback.php is present on the server
    Affected if The fallback.php file exists in the plugin directory
  4. Test if the directory traversal parameter is processed
    Send a crafted request to the fallback.php file with a path traversal payload such as /wp-content/plugins/luna-radio-player/js/fallback.php?path=../../../../wp-config.php and observe if file contents are returned
    Affected if The server returns contents of files outside the plugin directory

The environment is affected if the LUNA RADIO PLAYER plugin is installed with version 6.24.01.24 or lower and the js/fallback.php file is accessible and processes path parameters without proper sanitization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the LUNA RADIO PLAYER plugin to a version newer than 6.24.01.24 immediately. If no patched version is available, disable and remove the plugin until a fix is released. Alternatively, restrict access to the js/fallback.php file via web server configuration.

Recommended fix Moderate confidence

Version newer than 6.24.01.24 (check official source for exact version)

  1. Check the current version of the LUNA RADIO PLAYER plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate LUNA RADIO PLAYER and note the current version number
  4. Check the WordPress plugin repository or the developer's site (radioplayer.luna-universe.com) for the latest version
  5. If a version newer than 6.24.01.24 is available, update the plugin to that version
  6. After updating, verify the js/fallback.php file has been modified or removed as part of the security update
  7. Test that the radio player functionality still works correctly after the update
Caveat Review plugin changelog for any breaking changes between your current version and the updated version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10816 — 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-10816 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