CVE-2026-27989
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 Quanzo quanzo allows PHP Local File Inclusion.This issue affects Quanzo: from n/a through <= 1.0.10.
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 ThemeREX Quanzo WordPress theme (versions up to 1.0.10) contains a Local File Inclusion (LFI) vulnerability where the application allows unauthenticated users to manipulate filename parameters in PHP include/require statements. This improper input validation permits attackers to read sensitive local files from the server filesystem, potentially exposing configuration files, credentials, or other sensitive data.
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.
-
Confirm ThemeREX Quanzo theme is installedNavigate to wp-content/themes/ in your WordPress installation and verify the trx_quanzo theme folder exists. You can also check via WordPress admin under Appearance > Themes.Affected if The theme folder trx_quanzo exists in the themes directory
-
Identify installed theme versionOpen the style.css file within the trx_quanzo theme folder and locate the 'Version:' header in the file comments. Alternatively, check the theme details displayed in WordPress admin under Appearance > Themes.Affected if The version listed is 1.0.10 or lower (any version up to and including 1.0.10)
-
Locate file inclusion code patternsSearch theme PHP files for include, require, include_once, or require_once statements that use variables in the file path (e.g., include($filename), require($_GET['template'])). Examine files in the theme root and any includes/ folder.Affected if Files contain include/require statements with unsanitized user-controlled variables in the path parameter
-
Test parameter accessibilityIf the vulnerable parameter is identified, attempt a benign LFI test using a safe file path (e.g., ../../../../../../../../etc/passwd or ../../wp-config.php) via the identified parameter in a GET request to the affected page.Affected if The server returns content from the requested file, indicating the LFI vulnerability is present and exploitable
Your environment is affected if the ThemeREX Quanzo theme is installed with version 1.0.10 or lower and the theme contains file inclusion code that uses unsanitized input from user 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 dataApply the latest theme update (version 1.0.11 or later) which should implement proper input validation and sanitization on file inclusion parameters. If no update is available, implement strict allowlist validation on any user-supplied input used in include/require functions.
- 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-27989 — 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-27989 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