dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-5456

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Panda Video plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.4.0 via the 'selected_button' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 Panda Video WordPress plugin is vulnerable to Local File Inclusion (LFI) via the 'selected_button' parameter in all versions up to and including 1.4.0. Authenticated attackers with Contributor-level access or higher can include and execute arbitrary files on the server, leading to potential code execution and sensitive data exposure.

MitigationUpdate the Panda Video plugin to the latest patched version immediately. Review server logs for signs of exploitation and audit for any malicious files that may have been uploaded or executed.

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

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

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. Check Panda Video plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins > Panda Video and view the Version number, or inspect the plugin header in /wp-content/plugins/panda-video/ directory
    Affected if Version is 1.4.0 or lower (all versions up to 1.4.0 are affected)
  2. Verify plugin is active
    Confirm the Panda Video plugin is enabled in WordPress Admin > Plugins
    Affected if Plugin is installed and active, exposing the vulnerable endpoint
  3. Identify vulnerable endpoint
    The LFI flaw exists in the plugin's handling of the 'selected_button' parameter. Locate the plugin PHP file handling AJAX or form submissions that use this parameter
    Affected if Plugin code processes the 'selected_button' parameter without proper sanitization
  4. Review server access logs for exploitation attempts
    Search Apache/nginx access logs for requests to plugin endpoints containing 'selected_button' parameter with path traversal patterns (e.g., ../../etc/passwd)
    Affected if Logs show requests with 'selected_button' parameter containing '../' sequences or sensitive file paths
  5. Audit uploaded/included files
    Check /wp-content/uploads/ and plugin directories for any recently created or modified PHP files that may have been written via LFI exploitation
    Affected if Unexpected PHP files exist in upload directories or plugin folders that were not intentionally placed there

You are affected if the Panda Video plugin version is 1.4.0 or lower and the plugin is active, particularly if logs show exploitation attempts using the 'selected_button' parameter.

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 Panda Video plugin to the latest patched version immediately. Review server logs for signs of exploitation and audit for any malicious files that may have been uploaded or executed.

Recommended fix High confidence

Upgrade to the latest version of the Panda Video plugin (version higher than 1.4.0)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Panda Video' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. 6. Verify the updated version number after upgrading (should be higher than 1.4.0)

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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