CVE-2025-69112
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 · uneditedUnauthenticated Local File Inclusion in Planty <= 1.14.0 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 confidenceAn unauthenticated Local File Inclusion (LFI) vulnerability in Planty versions 1.14.0 and below allows remote attackers to read arbitrary files on the server by manipulating input parameters used in file inclusion operations.
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 Planty installation versionLocate the Planty installation directory and check version information in package.json, composer.json, or a VERSION file typically found in the application root. If using a package manager, run 'npm list planty' or 'composer show planty' to retrieve the installed version.Affected if The installed version is 1.14.0 or lower
-
Identify file inclusion endpointsReview application source code for includes, requires, or similar functions that accept user-supplied input. Search for patterns like 'include($_GET', 'require($_POST', or dynamic file inclusion functions that use request parameters.Affected if The application uses dynamic file inclusion with unsanitized user input from request parameters
-
Verify unauthenticated access to file inclusion functionalityAttempt to access the suspected file inclusion endpoint without providing authentication credentials. Check if the application allows unauthenticated requests to reach the vulnerable code path.Affected if The file inclusion functionality is accessible without authentication
-
Check for input validation on file path parametersInspect the code handling file inclusion requests to determine if directory traversal sequences (such as '../', '..\', or absolute paths) are being validated, sanitized, or blocked before being used in file operations.Affected if No input validation or sanitization is performed on file path parameters, allowing directory traversal
-
Review web server logs for exploitation attemptsExamine web server access logs for patterns indicating LFI exploitation attempts, such as requests containing '../', '..\', or common system file paths like '/etc/passwd' in query parameters.Affected if Logs show directory traversal patterns in requests to file inclusion endpoints
You are affected if Planty version 1.14.0 or lower is installed AND the application uses dynamic file inclusion with user-controlled input that is accessible without authentication and lacks proper input validation.
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 Planty to a version newer than 1.14.0. As a temporary measure, implement strict input validation on file path parameters and consider deploying a WAF to block directory traversal patterns.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69112 — 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-69112 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