CVE-2026-27985
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 Humanum humanum allows PHP Local File Inclusion.This issue affects Humanum: from n/a through <= 1.1.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 confidenceThe ThemeREX Humanum theme contains an improper control of filename vulnerability in PHP include/require statements, allowing local file inclusion. An attacker could exploit this to read sensitive files from the server or potentially achieve remote code execution depending on server configuration.
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 Humanum theme is installedNavigate to Appearance > Themes in WordPress admin, or inspect /wp-content/themes/ directory for the humanum theme folderAffected if ThemeREX Humanum theme is present in the WordPress installation
-
Identify installed theme versionOpen the style.css file in the theme directory (/wp-content/themes/humanum/) and locate the Version: header in the file comments, or check theme.php for version constantAffected if Version is lower than the patched version (compare against vendor release notes)
-
Verify vulnerable PHP include/require code existsSearch theme PHP files for include/require statements using dynamic input (e.g., grep -r 'include.*\$_' or 'require.*\$_REQUEST' in /wp-content/themes/humanum/)Affected if Theme files contain include/require statements that incorporate user-supplied parameters without sanitization (e.g., include($_GET['file']) or similar patterns)
-
Check for recent exploitation attemptsReview web server access logs (Apache error.log, Nginx access.log) for directory traversal patterns in theme-related requests (e.g., ../../etc/passwd in query parameters pointing to theme endpoints)Affected if Logs show LFI attempts targeting the theme's include/require functionality
Environment is affected if ThemeREX Humanum theme is installed with a vulnerable version containing unsanitized include/require statements that process user input.
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 dataUpdate to the latest patched version of the ThemeREX Humanum theme. As a temporary measure, disable the theme or deploy a WAF rule to block directory traversal patterns in query parameters.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27985 — 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-27985 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