CVE-2025-26905
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Estatik Estatik estatik allows PHP Local File Inclusion.This issue affects Estatik: from n/a through <= 4.3.0.
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 confidenceA path traversal vulnerability in the Estatik WordPress plugin (versions up to 4.3.0) allows remote attackers to perform Local File Inclusion (LFI) by manipulating file paths in PHP requests. This improper limitation of pathname to a restricted directory enables unauthorized access to sensitive files on the server.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Estatik plugin installationCheck the WordPress plugins directory at wp-content/plugins/ for a directory named 'estatik' or similar variant (estatik-real-estate-plugin, estatik-premium, etc.)Affected if The Estatik plugin directory exists in the WordPress plugins folder
-
Determine the installed versionOpen the main plugin PHP file (usually estatik.php) and locate the 'Version' header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entryAffected if The reported version is 4.3.0 or any earlier version (e.g., 4.2.9, 4.2.0, 3.x)
-
Identify vulnerable file upload or file include endpointsReview the plugin directory structure for PHP files that accept file path parameters, particularly in folders like /classes/, /controllers/, or /includes/; look for files containing functions like include(), require(), file_get_contents(), or readfile() that handle user-supplied path variablesAffected if The plugin contains PHP endpoints that accept file path parameters without sanitization via realpath() or whitelist validation
-
Verify if the plugin is actively processing requestsCheck WordPress error logs or server access logs for requests to Estatik plugin PHP files that contain path traversal patterns such as '../', '..%2F', or absolute paths like '/etc/passwd'Affected if Requests containing path traversal sequences targeted at Estatik plugin files are present in web server logs
A user is affected if the Estatik WordPress plugin is installed and the version is 4.3.0 or earlier, with vulnerable file-handling endpoints exposed to unauthenticated requests.
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 using realpath() and whitelist-based checks to ensure file paths remain within allowed directories; upgrade to the latest patched version when available.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26905 — 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-26905 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