CVE-2026-57803
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 Core allows PHP Local File Inclusion. This issue affects Struktur Core: 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 · moderate confidenceA PHP Local File Inclusion vulnerability exists in Select-Themes Struktur Core (struktur-core) plugin versions up to 2.5.1, where improper control of filenames in include/require statements allows attackers to include arbitrary local PHP files, potentially leading to 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
- 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 struktur-core plugin installationCheck your web root for the plugin directory at /wp-content/plugins/struktur-core/ or search for files containing 'struktur-core' in the plugins folderAffected if The plugin directory exists on the server
-
Identify installed versionOpen the main plugin file (typically structure-core.php or similar in the plugin root) and look for a version comment or constant, such as 'Version: x.x.x' or 'define( "STRUKTUR_CORE_VERSION", "..." )'Affected if The version number is 2.5.1 or lower, or no version is displayed (meaning it may be an unpatched copy)
-
Inspect include/require statements for dynamic input usageSearch the plugin PHP files for include(), require(), include_once(), or require_once() statements that use variables or request parameters without validation, such as 'include($some_var)' or 'include($_GET["file"])'Affected if Dynamic file inclusion using unsanitized variables or user input is found in the plugin code
-
Verify the vulnerability is remotely accessibleConfirm the vulnerable include code is reachable via a web request by checking if the affected PHP file is accessible through the WordPress frontend or AJAX endpointsAffected if The code containing the unsafe include/require is reachable via an HTTP request without authentication
You are affected if the struktur-core plugin is installed at version 2.5.1 or lower and contains dynamic include/require statements using unsanitized user input that 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 dataImplement strict input validation and use allowlist-based file inclusion logic to ensure only authorized, pre-defined files can be included. Validate all user-supplied input before using it in include/require statements.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57803 — 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-57803 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