CVE-2026-27337
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 AncoraThemes Chronicle - Lifestyle Magazine & Blog WordPress Theme chronicle allows PHP Local File Inclusion.This issue affects Chronicle - Lifestyle Magazine & Blog WordPress Theme: from n/a through <= 1.0.
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 the AncoraThemes Chronicle WordPress theme. The vulnerability allows attackers to include and execute arbitrary PHP files from the server through improper control of filename parameters in include/require statements, potentially leading to complete system compromise.
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 Chronicle theme installationNavigate to wp-content/themes/ directory and check for the chronicle folder, or list installed themes via WordPress admin under Appearance > ThemesAffected if The Chronicle theme folder exists in the WordPress themes directory
-
Identify Chronicle theme versionCheck the style.css file in wp-content/themes/chronicle/ for the 'Version:' header, or query the WordPress themes APIAffected if The installed version matches or precedes the patched version (version comparison required against known vulnerable range)
-
Locate vulnerable file inclusion codeSearch theme PHP files for include/require statements using dynamic variables or user-supplied input without sanitization: grep -r 'include\|require' wp-content/themes/chronicle/ | grep -E '\$_(GET|POST|REQUEST'Affected if Unfiltered filename parameters are used in include/require statements within theme files
-
Verify parameter injection pointExamine the identified include/require calls for direct use of $_GET, $_POST, or $_REQUEST in the filename argument without sanitization functions like basename() or realpath()Affected if User-controlled input flows directly into file inclusion functions without validation
-
Test LFI condition (if authorized)In an authorized testing environment, attempt a controlled request with a benign path traversal payload to the suspected vulnerable parameter (e.g., ?file=../../../../etc/passwd)Affected if The server returns file contents from outside the intended directory, confirming LFI
Users are affected if the Chronicle theme is installed and contains unpatched file inclusion code that allows path traversal through unsanitized 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 dataReplace or update the Chronicle theme to a patched version once available, or implement strict input validation and whitelist-based file inclusion controls to prevent path traversal and unauthorized 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-27337 — 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-27337 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