CVE-2026-25027
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 ThemeMove Unicamp unicamp allows PHP Local File Inclusion.This issue affects Unicamp: from n/a through <= 2.7.1.
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 confidenceThe ThemeMove Unicamp WordPress theme contains a Local File Inclusion (LFI) vulnerability where improper control of filename parameters in PHP include/require statements allows attackers to read sensitive files on the server. This is a high-severity issue exploitable remotely 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
- 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.
-
Confirm Unicamp theme is installedInspect WordPress theme directory (wp-content/themes/) for the unicamp folder, or check via WordPress admin appearance themes listAffected if The Unicamp theme by ThemeMove is present in the WordPress installation
-
Identify installed theme versionCheck theme style.css header for Version: field, or look for version defined in theme functions filesAffected if Version cannot be determined or is within an affected range (compare to any published vulnerable versions)
-
Locate file inclusion code in themeSearch theme PHP files for include, require, include_once, or require_once statements that use variables in the filename parameter (e.g., include($file), require($_GET['template']))Affected if Dynamic file inclusion using unsanitized user input is found in theme PHP files
-
Check for vulnerable parameter exposureExamine identified file inclusion code for direct use of $_GET, $_POST, or other user-supplied parameters without validation functions like basename() or realpath()Affected if Filename parameters accept user input without sanitization or allow path traversal sequences (../)
-
Test accessibility of vulnerable endpointsIf file inclusion parameters are identified, attempt to access them via HTTP requests with path traversal (e.g., ?file=../../../../wp-config.php)Affected if The server responds with file contents from outside the intended directory
A user is affected if the Unicamp theme is installed and its PHP code contains dynamic file inclusion using unsanitized user-controlled parameters that can be exploited via directory traversal.
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 on all file inclusion parameters using allowlists, avoid dynamic file inclusion based on user input, and sanitize paths using basename() and realpath() functions to prevent directory traversal.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25027 — 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-2026-25027 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