CVE-2026-39677
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 Creatives_Planet Emphires emphires allows PHP Local File Inclusion.This issue affects Emphires: from n/a through <= 3.9.
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 PHP Local File Inclusion (LFI) vulnerability in the Emphires theme by Creatives_Planet. The vulnerability allows attackers to include arbitrary local files on the server due to improper control of filenames in include/require statements. This can lead to sensitive data exposure, code execution, or further compromise of the system.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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.
-
Locate Emphires theme installationSearch your web server directories for the Emphires theme files, typically found in wp-content/themes/emphires or similar theme directoriesAffected if The Emphires theme is present in the environment
-
Determine installed versionCheck the theme's style.css or theme.json file for the version declaration, or examine any version.php or version.txt file within the theme folderAffected if The installed version falls within any affected range or is unknown/unpatched
-
Identify PHP files with include/require statementsSearch the theme's PHP files for include, include_once, require, or require_once statements that accept user-supplied input (e.g., parameters from GET/POST requests)Affected if Dynamic file inclusion using user input is found without apparent sanitization
-
Inspect input validation on file inclusion codeExamine the identified include/require code paths to verify whether $_GET, $_POST, or similar superglobals are used directly as file paths, and check if basename(), realpath(), or whitelist validation is appliedAffected if User input is used in include/require statements without sanitization functions like basename() or realpath()
-
Confirm vulnerability is web-accessibleVerify that the vulnerable PHP file and its input parameters are accessible via HTTP/HTTPS requests to the web serverAffected if The vulnerable code can be reached through web requests
If the Emphires theme is installed and its PHP code contains include/require statements using unsanitized user input that is web-accessible, the environment is likely affected by this LFI vulnerability.
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 dataFix the vulnerable include/require statements by implementing strict input validation, using allowlists for permitted files, or avoiding dynamic file inclusion entirely. Upgrade to a patched version if 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-39677 — 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-39677 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