CVE-2026-27383
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 RadiusTheme Metro metro allows PHP Local File Inclusion.This issue affects Metro: from n/a through <= 2.13.
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 exists in the RadiusTheme Metro WordPress theme (versions <= 2.13). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code or access sensitive files on the server.
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.
-
Identify if Metro theme is installedNavigate to wp-content/themes/ directory or check via WordPress admin under Appearance > Themes. Look for a folder named 'metro' or 'metro-child'.Affected if The metro theme folder exists in the WordPress themes directory.
-
Determine the installed Metro theme versionOpen the file 'style.css' within the metro theme folder and locate the 'Version:' declaration in the theme header comments. Alternatively, check version in theme.json or readme.txt if present.Affected if The reported version number is 2.13 or lower.
-
Identify PHP files that perform file inclusionsSearch the metro theme folder for PHP files containing 'include', 'require', 'include_once', or 'require_once' statements. Review each for dynamic file path usage.Affected if The theme contains PHP include/require statements that construct file paths dynamically.
-
Locate parameters that control file pathsExamine identified include/require statements for variables used in file paths (e.g., $_GET, $_POST, $_REQUEST). Trace back to find which URL parameters control the included file path.Affected if User-supplied input (via GET, POST, or REQUEST) is directly or indirectly used in file inclusion statements without proper validation.
-
Verify lack of input validation on file inclusion parametersReview the code handling the identified parameters for whitelist validation, sanitization, or path traversal prevention (such as checking for '../' or absolute paths).Affected if No whitelist-based filtering or strict input validation is present on the file inclusion parameters.
You are affected if the Metro theme version is 2.13 or lower AND the theme contains PHP file inclusion logic that uses unsanitized user input to control which files are included.
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 whitelist-based filtering on all file inclusion parameters, ensuring only allowed files can be included and preventing path traversal sequences.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27383 — 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-27383 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