CVE-2026-27987
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 The Qlean the-qlean allows PHP Local File Inclusion.This issue affects The Qlean: from n/a through <= 2.12.
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 · high confidenceLocal File Inclusion vulnerability in ThemeREX The Qlean theme allows attackers to control filename parameters in PHP include/require statements, potentially enabling remote code execution by including malicious local PHP files.
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 the installed ThemeREX The Qlean theme versionAccess the WordPress installation directory and locate the theme folder (typically /wp-content/themes/the-qlean/). Open the style.css file in the theme root and look for the 'Version:' declaration in the file header comments.Affected if The version listed is 2.12 or lower.
-
Verify the vulnerable include/require pattern existsSearch within the theme directory for PHP files that contain include, include_once, require, or require_once statements which use variables or request parameters as the file path (e.g., include($file), include($_GET['file']). Use grep or manually inspect PHP files in the theme folder.Affected if The theme code contains dynamic file inclusion statements that use unsanitized input from $_GET, $_POST, or other user-controlled sources.
-
Confirm the path traversal attack surfaceReview the identified vulnerable include/require code paths to determine if the application accepts file paths that could be manipulated with ../ sequences to traverse outside the intended directory.Affected if The file inclusion logic does not validate or sanitize input to prevent directory traversal sequences.
-
Check web server access logs for exploitation attemptsReview Apache, Nginx, or other web server access logs for requests to the WordPress site that contain ../ patterns in query parameters, particularly targeting PHP files within the theme directory.Affected if Logs show path traversal attempts (e.g., ?file=../../wp-config.php) targeting the theme's file inclusion functionality.
You are affected if the The Qlean theme version is 2.12 or lower AND the theme contains dynamic file inclusion code that processes unsanitized user input, allowing path 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 dataUpgrade to the latest version of The Qlean theme (2.13+) which should contain proper input validation for include/require statements, or remove/disable the vulnerable theme if no patch is available.
- 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-27987 — 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-27987 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