CVE-2025-60202
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Kyle Phillips Favorites favorites allows PHP Local File Inclusion.This issue affects Favorites: from n/a through <= 2.3.6.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Kyle Phillips Favorites plugin (versions up to 2.3.6). The application fails to properly validate or sanitize user-supplied input used in PHP include/require statements, allowing attackers to manipulate file paths and potentially read sensitive server files or achieve remote code execution.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed plugin versionLocate the Kyle Phillips Favorites plugin in your WordPress wp-content/plugins directory. Check the main plugin PHP file (typically favorites.php or similar) for the version number in the plugin header comment, or check the readme.txt file for the Version field.Affected if The installed version is 2.3.6 or any earlier version number.
-
Verify the plugin is activeIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and confirm whether the Favorites plugin by Kyle Phillips is currently activated.Affected if The plugin is active and the version is 2.3.6 or lower.
-
Inspect for file inclusion endpointsExamine the plugin PHP files for code that uses include, include_once, require, or require_once statements where user-supplied parameters (such as GET, POST, or cookie values) are used as all or part of the file path.Affected if The plugin contains PHP code that dynamically includes files based on user input without proper validation or sanitization.
-
Check for path traversal patternsSearch the plugin source code for patterns where user input is concatenated with file paths or used directly in inclusion functions, especially without sanitization functions like basename(), realpath(), or allowlist checks.Affected if User-controllable input is used in include/require statements without adequate path validation.
Your environment is affected if the Kyle Phillips Favorites plugin is installed, active, and running at version 2.3.6 or lower.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of the Favorites plugin that implements proper input validation on file inclusion operations, or apply input sanitization/allowlisting to prevent path traversal in include/require statements.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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