CVE-2026-27990
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 ThemeREX ConFix confix allows PHP Local File Inclusion.This issue affects ConFix: from n/a through <= 1.013.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in ThemeREX ConFix (version 1.013 and below) where improper control of filename parameters in PHP include/require statements allows attackers to read sensitive local 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
- 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.
-
Verify ThemeREX ConFix is installedSearch the web root directory for files or directories named 'confix', 'themerex', or related components. Check for ThemeREX-related PHP files or plugins in the application structure.Affected if ThemeREX ConFix or related ThemeREX components are present on the server
-
Check the installed versionLocate version information in the ThemeREX ConFix installation, such as a version file, header comments in PHP files, or the plugin/theme metadata. Compare the version number to 1.013 or below.Affected if The installed version is 1.013 or any version lower than 1.013
-
Identify exposed PHP include/require handlersReview the PHP source files in the ThemeREX ConFix installation for include(), require(), include_once(), or require_once() statements that use variable or user-controlled input as the filename parameter.Affected if PHP include/require statements accept variable filename parameters without proper validation
-
Test for accessible file parameter inputLocate web-accessible endpoints or parameters that accept file paths as input (for example, URL parameters like 'file=', 'path=', 'page=', or similar). Attempt to access a known safe local file (such as /etc/passwd on Linux or a known config file) to confirm the LFI behavior.Affected if The application accepts file path input through web parameters and returns file contents without proper validation
The environment is affected if ThemeREX ConFix version 1.013 or lower is installed and the application exposes file parameter handling via PHP include/require statements that can be manipulated to read arbitrary local files.
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 the latest version of ThemeREX ConFix if available, or implement strict input validation with whitelist-based file inclusion controls to prevent arbitrary file access.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27990 — 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-27990 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