CVE-2025-60051
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 AncoraThemes Rare Radio rareradio allows PHP Local File Inclusion.This issue affects Rare Radio: from n/a through <= 1.0.15.1.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the Rare Radio theme by AncoraThemes. The vulnerability stems from improper control of filename parameters in PHP include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code by including malicious local files.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Rare Radio theme is installedCheck your WordPress themes directory (wp-content/themes/) for a folder named 'rare-radio' or similar. In the theme folder, check style.css for the theme name and version in the header comments.Affected if The theme folder 'rare-radio' exists in the themes directory
-
Locate the vulnerable file inclusion codeSearch PHP files in the theme for include, require, include_once, or require_once statements that use variables in the file path (e.g., include($_GET['file']). Look for parameters that could accept file paths.Affected if PHP files contain include/require statements using unsanitized variables, especially $_GET or $_REQUEST parameters
-
Identify the vulnerable parameterExamine the identified include/require code to determine which URL parameter controls the file path (common names: file, page, template, include, path, slug). Test if the parameter accepts relative paths like ../../Affected if A URL parameter controls the included file path without proper validation or whitelisting
-
Check if the vulnerable endpoint is accessibleAttempt to access the suspected vulnerable URL endpoint with a path traversal payload (e.g., ?file=../../wp-config.php). If the file content is rendered or included, the vulnerability is present.Affected if The application returns content from files outside the intended directory when path traversal characters are used
-
Compare installed version to any known patched versionIf version information is found in the theme header or a version file, compare it against any patched version provided by AncoraThemes. Without a known patched version, treat all versions as potentially vulnerable.Affected if The installed version is older than the patched version released by AncoraThemes
A user is affected if the Rare Radio theme is installed, contains unsanitized file inclusion parameters accessible via URL, and accepts path traversal characters to include arbitrary local files.
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.
dbcve · scopedUpdate to a patched version of Rare Radio after consulting with AncoraThemes, or implement strict input validation and whitelist-based filtering on all file inclusion parameters to prevent path traversal.
Latest version from AncoraThemes (version > 1.0.15.1)
- Log in to your WordPress admin dashboard
- Navigate to Appearance > Themes
- Locate the Rare Radio theme
- Check if an update is available and update to the latest version
- If no update appears in WordPress, manually download the latest version from AncoraThemes marketplace or theme provider
- Before updating, create a full backup of your WordPress site
- After updating, verify the theme version in Themes section to confirm the update was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-60051 — 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-60051 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