CVE-2025-69144
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 Preservation <= 1.10 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 exists in the Preservation plugin for versions 1.10 and below, allowing remote attackers to read sensitive local files on the server without authentication.
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.
-
Locate the Preservation plugin installationIdentify the directory where the Preservation plugin is installed on the server. Common locations include /wp-content/plugins/preservation/ or similar paths depending on the CMS platform.Affected if The plugin directory exists on the server
-
Determine the installed versionCheck the plugin metadata file (such as readme.txt, plugin header comment, or version file) within the Preservation plugin directory to read the currently installed version number.Affected if The installed version is 1.10 or lower
-
Identify the vulnerable endpointLocate the PHP file(s) within the plugin that handle file inclusion or file loading operations. Examine the code for parameters that accept user input for file paths (common parameter names include 'file', 'path', 'page', 'template', 'include', or similar).Affected if The plugin contains files that accept file path parameters without proper sanitization
-
Test unauthenticated accessAttempt to access the identified endpoint using a web request without providing authentication credentials. Send a request with a typical LFI payload such as ../../../../etc/passwd or similar path traversal sequence.Affected if The server returns file contents from the requested path without requiring authentication
-
Check for sensitive file exposureUsing the identified vulnerable parameter, attempt to read known sensitive local files such as configuration files containing database credentials, configuration settings, or system files accessible from the web root.Affected if Sensitive file contents are returned in the response
The environment is affected if the Preservation plugin is installed with version 1.10 or below and the LFI endpoint is accessible without authentication.
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 the Preservation plugin to version 1.11 or later to patch the LFI vulnerability. If an update is unavailable, disable the plugin until a fix is released.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69144 — 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-69144 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