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

CVE-2025-69159

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 Printo <= 1.11 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 · high confidence

Unauthenticated Local File Inclusion (LFI) vulnerability in Printo version 1.11 and earlier allows remote attackers to read arbitrary files on the server filesystem by manipulating input parameters that handle file paths without proper validation or sanitization.

MitigationUpgrade Printo to the latest version (currently unknown, check vendor advisories) or implement strict input validation and path sanitization to prevent directory traversal sequences in file inclusion functions.

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. Locate Printo installation
    Search web server directories for 'Printo' or 'printo' folder names, or check HTTP responses for 'Printo' in headers or page content
    Affected if Printo web application is found on the server
  2. Determine installed version
    Check for version files (version.php, about, or changelog) within the Printo installation directory, or inspect HTTP headers/banners for version strings
    Affected if Installed version is 1.11 or earlier, or version cannot be determined but is presumed old
  3. Identify file inclusion endpoints
    Review source code for file inclusion functions (include, require, file_get_contents with variable input) that handle file path parameters, or fuzz common parameter names (file, path, page, template, lang) in HTTP requests
    Affected if File inclusion functions accept user-controlled input without validation
  4. Check unauthenticated access
    Send HTTP requests to identified file inclusion parameters without authentication credentials to verify they are accessible without login
    Affected if Unauthenticated requests can reach file inclusion parameters that handle file paths
  5. Verify directory traversal acceptance
    Send test requests with directory traversal sequences (../../../../etc/passwd or similar) to file inclusion parameters to confirm the application accepts path traversal
    Affected if The application returns file contents from paths outside the intended directory, indicating LFI is present

The server is affected if Printo version 1.11 or earlier is installed and unauthenticated file inclusion parameters accepting path traversal input are accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Printo to the latest version (currently unknown, check vendor advisories) or implement strict input validation and path sanitization to prevent directory traversal sequences in file inclusion functions.

Recommended fix Moderate confidence

Latest stable Printo release (version 1.12 or higher)

  1. 1. Backup your current Printo installation and database before making any changes.
  2. 2. Check your currently installed Printo version in your WordPress admin panel or via file inspection.
  3. 3. Navigate to the official WordPress plugin repository or Printo's official distribution channel.
  4. 4. Download the latest available version of Printo (version 1.12 or higher).
  5. 5. Deactivate the current Printo plugin/theme.
  6. 6. Replace the existing Printo files with the updated version.
  7. 7. Reactivate the plugin/theme.
  8. 8. Verify the LFI vulnerability is no longer exploitable by testing file inclusion attempts are blocked.
Caveat Review changelog for any deprecated features or template changes between 1.11 and the latest version

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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