CVE-2025-14431
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in THEMELOGI Navian navian allows PHP Local File Inclusion.This issue affects Navian: from n/a through <= 1.5.4.
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 confidenceTHEMELOGI Navian theme <= 1.5.4 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in include/require statements. An attacker could potentially include arbitrary local PHP files, leading to information disclosure or remote code execution depending on system context.
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 if Navian theme is installedLocate the theme directory - typically in wp-content/themes/navian/ for WordPress installations. Check for the existence of style.css or theme files containing 'Navian' or 'THEMELOGI' in metadata.Affected if The Navian theme directory exists in the webroot.
-
Determine installed Navian theme versionOpen the theme's style.css or functions.php file and locate the version comment or Version: header field. Compare the version number to the affected range (1.5.4 and below).Affected if The installed version is 1.5.4 or any earlier version.
-
Locate PHP files with include/require statements using dynamic variablesSearch the theme directory for PHP files containing include, require, include_once, or require_once statements where the file path comes from $_GET, $_POST, or $_REQUEST parameters (e.g., include($_GET['file']).Affected if PHP files in the theme contain dynamic file inclusion using user-supplied input without proper sanitization.
-
Identify accessible endpoints leveraging the vulnerable codeReview the identified include/require files to determine which URL parameters trigger the LFI (e.g., ?file=path/to/file). Test by requesting the suspected endpoint with a benign path like ../../wp-config.php.Affected if The vulnerable parameter is reachable via HTTP request and responds with file contents when given a traversal path.
-
Check if the web server has traversal protectionsInspect any existing WAF rules, web server configuration (nginx/apache), or application-level filters that may block directory traversal patterns (../, ..\) in query parameters.Affected if No traversal protections exist and the vulnerable parameter is exposed to unauthenticated users.
A user is affected if the Navian theme version is 1.5.4 or lower AND the theme contains PHP files that use user input in include/require statements without sanitization, and those endpoints are accessible on the web server.
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 to a patched version of Navian theme if available; otherwise, implement strict input validation on include/require parameters or disable the vulnerable functionality until a fix is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14431 — 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-14431 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