dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-69147

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Unauthenticated Local File Inclusion in Putter <= 1.17 versions.

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

Unauthenticated Local File Inclusion vulnerability in Putter plugin versions 1.17 and below allows remote attackers to read arbitrary files on the server filesystem without authentication. The LFI flaw could expose sensitive configuration files, credentials, or other system files.

MitigationUpdate Putter to the latest version (greater than 1.17) when available. Until patched, consider restricting web server access or implementing WAF rules to block directory traversal patterns in requests.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Putter plugin installation
    Check the WordPress plugins directory (typically /wp-content/plugins/) or list installed plugins via WP-CLI: wp plugin list --status=active --format=csv
    Affected if Putter plugin is found in the active plugins list
  2. Determine installed Putter version
    Open the main Putter plugin file (e.g., putter.php) and locate the version comment/constant, or check readme.txt for the 'Stable tag' entry, or run: grep -i 'Version' /path/to/putter/putter.php
    Affected if Version is 1.17 or lower (the vulnerable version range)
  3. Verify the plugin is active
    Confirm Putter is enabled in WordPress admin under Plugins > Installed Plugins, or via WP-CLI: wp plugin status putter
    Affected if Plugin status shows as 'Active' - the vulnerability is only exploitable when the plugin is active
  4. Locate vulnerable file operation code
    Search the putter plugin directory for file include/require statements using functions like include, require, file_get_contents, or readfile that accept user-controlled path parameters, e.g., grep -rn 'file' /wp-content/plugins/putter/ | grep -E '\$_GET|\$_REQUEST'
    Affected if PHP files in the plugin handle file paths via request parameters without sanitization

If Putter plugin version 1.17 or lower is installed and active, the system is affected by this unauthenticated LFI vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Putter to the latest version (greater than 1.17) when available. Until patched, consider restricting web server access or implementing WAF rules to block directory traversal patterns in requests.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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