CVE-2026-57802
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 Select-Themes Struktur allows PHP Local File Inclusion. This issue affects Struktur: from n/a before 2.7.
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 PHP Local File Inclusion (LFI) vulnerability in the Select-Themes Struktur theme (versions <= 2.5.1) allows attackers to control file paths used in PHP include/require statements. This stems from improper validation of user-supplied input before passing it to file inclusion functions, potentially enabling arbitrary code execution if attackers can upload files or poison log files.
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.
-
Identify if Struktur theme is installedLocate the theme directory - typically in wp-content/themes/struktur/ or similar path depending on the CMS. Check for theme.json, style.css, or theme PHP files containing 'Struktur' or 'Select-Themes' in the metadata.Affected if The Struktur theme by Select-Themes is present in the web root
-
Determine the installed theme versionOpen the theme's main style.css file or theme.json and look for the 'Version:' field in the header comments, or check version defined in the theme's PHP files.Affected if The version number is 2.5.1 or lower, or no version is specified but the theme appears to be an older release
-
Locate PHP files using include/require with user inputSearch the theme directory for patterns like 'include($_GET', 'require($_POST', 'include($_REQUEST', or similar constructs where user-supplied parameters are used directly in file inclusion functions. Use: grep -r "include.*\$_GET\|require.*\$_REQUEST" /path/to/theme/Affected if PHP files in the theme directly use $_GET, $_POST, $_REQUEST, or similar superglobals in include, require, include_once, or require_once statements without sanitization
-
Verify the vulnerable file inclusion is accessibleTest if the affected PHP files can be accessed via web requests. Identify the endpoint/parameter that triggers the include (e.g., ?file=template.php). Attempt a benign test request with a controlled value to confirm the parameter is reflected in include statements.Affected if The file inclusion code is reachable via HTTP requests and the parameter controls which file gets included
A user is affected if the Struktur theme version is 2.5.1 or lower AND the theme contains PHP files that directly use user-supplied input in include/require statements and these are 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 dataUpdate to a patched version if available. Otherwise, implement strict input validation using allowlists, avoid using user input in include/require statements, disable allow_url_include, and consider setting open_basedir restrictions.
- 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-57802 — 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-57802 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