CVE-2026-27340
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 Apollo | Night Club, DJ Event WordPress Theme apollo allows PHP Local File Inclusion.This issue affects Apollo | Night Club, DJ Event WordPress Theme: from n/a through <= 1.3.1.
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 confidenceA Local File Inclusion (LFI) vulnerability exists in the AncoraThemes Apollo WordPress Theme (versions up to 1.3.1) where user-supplied input is improperly used in PHP include/require statements without proper sanitization. This allows attackers to include arbitrary PHP files from the local server, potentially leading to code execution or sensitive file disclosure.
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 Apollo theme is installedNavigate to wp-content/themes/apollo or check WordPress admin under Appearance > Themes to verify the Apollo theme is present on the siteAffected if Apollo theme is installed and active on the WordPress site
-
Identify installed theme versionOpen wp-content/themes/apollo/style.css and locate the 'Version:' header in the theme comments, or check version info in functions.phpAffected if The version is 1.3.1 or below, or if no version is declared and the theme files are from an older release
-
Locate vulnerable include/require patternsSearch theme PHP files (particularly in includes/ or functions.php) for include(), require(), include_once(), or require_once() statements that use variables without sanitization, such as include($_GET['...']) or require($var)Affected if Any include/require statement uses raw $_GET, $_POST, or $_REQUEST variables to construct file paths
-
Verify parameter exposure in theme filesInspect PHP files that handle template redirects or AJAX endpoints within the theme; look for parameters like 'file', 'path', 'template', or 'include' that are passed to include/require functions without validationAffected if URL-accessible parameters exist that can be manipulated to inject directory traversal sequences (such as ../../) leading to arbitrary file inclusion
A site is affected if it runs the AncoraThemes Apollo theme version 1.3.1 or below and contains include/require statements that accept unsanitized user input via URL parameters.
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 theme. If no patch is available, audit and fix the file inclusion logic to use safe functions like basename() and realpath() for input validation, or replace dynamic includes with whitelisted file references.
- 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-27340 — 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-27340 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