CVE-2026-27334
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 dan_fisher Alchemists alchemists allows PHP Local File Inclusion.This issue affects Alchemists: from n/a through <= 4.6.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 confidenceA Local File Inclusion (LFI) vulnerability in the dan_fisher Alchemists WordPress theme (versions up to 4.6.0) allows attackers to manipulate file inclusion paths in PHP include/require statements. This could enable reading sensitive server files or, in certain configurations, remote code execution.
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 Alchemists theme installationCheck WordPress themes directory (wp-content/themes/) for the 'alchemists' theme folder, or view installed themes via WordPress admin under Appearance > ThemesAffected if The 'alchemists' theme folder exists in the WordPress themes directory
-
Determine installed theme versionOpen the theme's style.css file (wp-content/themes/alchemists/style.css) and locate the 'Version:' header in the file comment block. Compare the version number to 4.6.0Affected if The theme version is 4.6.0 or lower
-
Identify vulnerable file inclusion codeSearch theme PHP files for dynamic include/require statements that use user-input parameters (e.g., grep for 'include($_GET' or 'require($_REQUEST' within wp-content/themes/alchemists/)Affected if PHP files contain include/require statements using unsanitized $_GET, $_POST, or $_REQUEST variables to construct file paths
-
Check for accessible file inclusion parametersReview theme files that handle template redirects or AJAX actions to identify which parameters control file inclusion, then test if these parameters are accessible via web requestsAffected if Parameters controlling include/require are accessible via URL query strings or POST data without authentication or validation
-
Inspect server access logs for exploitation attemptsReview web server access logs (Apache error.log, Nginx access.log) for suspicious requests containing '../' or file path patterns in query parameters targeting theme filesAffected if Logs show requests with directory traversal patterns (../) or direct file path attempts in parameters matching theme file inclusion functions
A user is affected if the Alchemists theme version is 4.6.0 or lower AND the theme contains dynamic file inclusion code accessible via web 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 dataImplement strict input validation using a whitelist approach for file inclusion paths, ensuring only permitted files can be included. Consider using basename() and realpath() to normalize and validate paths before inclusion.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27334 — 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-27334 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