CVE-2025-60072
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 Processby Anchor smooth scroll anchor-smooth-scroll allows PHP Local File Inclusion.This issue affects Anchor smooth scroll: from n/a through <= 1.0.2.
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 confidenceThe Anchor smooth scroll plugin for PHP contains a file inclusion vulnerability where user-supplied input is used in include/require statements without proper sanitization. This allows attackers to manipulate file paths via directory traversal to include arbitrary local files, potentially exposing sensitive system files or executing malicious PHP code.
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 Anchor smooth scroll plugin is installedSearch for files named 'anchor-smooth-scroll' or similar in the web document root, typically under /wp-content/plugins/ (for WordPress) or in the application's includes/modules directoriesAffected if The plugin directory exists on the server
-
Determine the installed versionCheck for a version file (like version.php, README, or composer.json) within the plugin directory to identify the exact version numberAffected if The version cannot be determined or is unknown and the plugin is present
-
Locate file inclusion codeSearch the plugin source code for 'include', 'require', 'include_once', or 'require_once' statements that use variables in the file path (e.g., include($_GET['page']) or require($file)Affected if Dynamic file inclusion using user-supplied input is found in the code
-
Check if the vulnerable parameter is accessibleIdentify URL parameters or input fields that control the included file path (common names include 'page', 'file', 'path', 'template', or 'include'); test if these accept directory traversal sequences like '../'Affected if User-controlled input can be passed to include/require functions without sanitization
-
Verify directory traversal is possibleAttempt to access a known file via the suspected parameter (e.g., ?page=../../../../etc/passwd or ?file=../../config.php), observing if file contents are returned or included in the responseAffected if The application returns contents of files outside the intended directory
A user is affected if the Anchor smooth scroll plugin is installed and contains dynamic include/require statements that accept unsanitized user input, allowing directory traversal to access 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.
From vendor dataImplement strict input validation and whitelist-based filtering on any parameters used in include/require statements, ensuring only predefined, safe file paths can be included. Alternatively, refactor to avoid dynamic file inclusion entirely.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60072 — 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-60072 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