dbcve.org
PandaWordPress extension · Axiomthemes

CVE-2025-60050

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 1.21 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in axiomthemes Panda panda allows PHP Local File Inclusion.This issue affects Panda: from n/a through <= 1.21.

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

The Panda WordPress theme by axiomthemes contains a PHP Local File Inclusion vulnerability (CWE-98) in versions through 1.21. The vulnerability stems from improper validation of user-supplied input used in PHP include/require statements, allowing attackers to include arbitrary PHP files from the local filesystem or potentially remote sources.

MitigationUpdate to the latest patched version of the Panda theme. If no patch is available, implement input validation/sanitization on all file inclusion parameters and disable allow_url_include in PHP configuration.

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
PandaWordPress extension
Affected:<= 1.21

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify the installed theme version
    Access the WordPress admin dashboard, navigate to Appearance > Themes, and locate the Panda theme to view its version number. Alternatively, check the style.css file in wp-content/themes/panda/ for the 'Version:' header in the theme comments.
    Affected if The displayed version is 1.21 or any lower version number, indicating the theme is within the affected range (<= 1.21).
  2. Locate file inclusion code in the theme
    Search the theme files (particularly PHP files in wp-content/themes/panda/) for include, require, include_once, or require_once statements that use variables derived from request parameters (e.g., $_GET, $_POST, $_REQUEST). Look for patterns like 'include($_REQUEST["..."]' or 'require($var)' without sanitization.
    Affected if Such vulnerable file inclusion code exists in the theme, meaning user-supplied input could be used to control which files are included.
  3. Identify the vulnerable parameter
    Examine any found file inclusion code to determine which specific HTTP parameter (GET, POST, or REQUEST) feeds the include/require statement. Test sending a request with a benign path value to confirm the parameter is processed.
    Affected if A parameter controllable via HTTP request is directly used in an include/require statement without validation, indicating the vulnerability is present and exploitable.
  4. Check PHP configuration for remote inclusion support
    Review the PHP configuration file (php.ini) and verify the setting for 'allow_url_include'. If accessible via the site, create a PHPinfo page or check the server configuration to confirm whether this directive is enabled.
    Affected if allow_url_include is set to On, which would allow remote file inclusion in addition to local file inclusion, increasing the severity of exploitation.

You are affected if your installed Panda theme version is 1.21 or lower AND the theme contains file inclusion code that uses unsanitized user input from HTTP parameters.

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.

From vendor data
Upgrade available Upgrade to a release after 1.21
Interim mitigation

Update to the latest patched version of the Panda theme. If no patch is available, implement input validation/sanitization on all file inclusion parameters and disable allow_url_include in PHP configuration.

Fix this in Panda Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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