CVE-2026-57792
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 Mikado-Themes Dør dor allows PHP Local File Inclusion.This issue affects Dør: from n/a through <= 2.4.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 · moderate confidenceA PHP Local File Inclusion vulnerability in Mikado-Themes Dør theme (versions up to 2.4.1) allows attackers to include arbitrary PHP files from the server through improper control of filename parameters used in include/require statements, potentially leading to 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
- 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 the Dør theme installation directorySearch for directories named 'dor', 'dør', or 'mikado' in the web root, typically under wp-content/themes/ for WordPress or under /themes/ for other PHP applications.Affected if The Dør theme by Mikado-Themes is installed on the server.
-
Identify the installed Dør theme versionCheck theme.json, style.css header, or version.php within the theme folder for a 'Version:' field. Compare the version number to 2.4.1 - any version 2.4.1 or lower is affected.Affected if The installed version is 2.4.1 or lower.
-
Search for PHP include/require statements using dynamic variablesGrep the theme files for patterns like 'include($_', 'require($_', 'include($_GET', 'require($_POST', or similar constructs where user-supplied parameters flow directly into include/require functions without sanitization.Affected if Dynamic file inclusion using $_GET, $_POST, or $_REQUEST parameters is found in the theme code.
-
Examine the affected file inclusion parametersReview the specific include/require files identified in step 3. Check if the filename parameter is processed through basename() or realpath() for sanitization, or if it accepts directory traversal sequences like '../'.Affected if The file inclusion does NOT use basename() or realpath() to sanitize the filename and allows path traversal.
You are affected if the Dør theme version is 2.4.1 or lower AND the theme contains include/require statements that use unsanitized user input from request 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 dataImplement strict input validation using allowlists for file paths, avoid using user-supplied input directly in include/require statements, and use basename() or realpath() functions to sanitize path inputs.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57792 — 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-57792 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