CVE-2026-28055
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 ThemeREX M.Williamson williamson allows PHP Local File Inclusion.This issue affects M.Williamson: from n/a through <= 1.2.11.
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 confidenceLocal File Inclusion (LFI) vulnerability in ThemeREX M.Williamson WordPress theme allows attackers to include arbitrary PHP files from the server through improper control of filename parameters in PHP include/require statements. This can lead to sensitive file disclosure or remote code execution if attacker-controlled input can reach the include function.
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.
-
Confirm ThemeREX M.Williamson theme is installedNavigate to wp-content/themes/ directory and verify the theme folder exists, or check via WordPress admin dashboard under Appearance > ThemesAffected if The theme folder 'm-williamson' or similar ThemeREX M.Williamson theme directory is present
-
Determine the installed theme versionOpen the style.css file in the theme directory and locate the 'Version:' header in the file comments, or check theme.json if presentAffected if The version number found is lower than the patched version (compare against any available version information from ThemeREX)
-
Locate vulnerable file inclusion codeSearch the theme directory for PHP files containing include, require, include_once, or require_once statements that use variables in the file path (e.g., include($_GET['file'] or include($filename)) without proper sanitizationAffected if PHP files with unsanitized variable-based include/require statements are found in the theme
-
Identify the vulnerable parameterExamine the identified include/require statements to determine which GET/POST parameter controls the filename (commonly 'file', 'page', 'template', or 'path' parameters)Affected if A parameter like 'file', 'page', or 'template' is used in the include statement without validation
-
Test if the parameter is accessibleReview the theme's PHP files to determine if the vulnerable parameter is accessible via HTTP requests (check if the code runs in the frontend without authentication)Affected if The vulnerable include code executes on frontend pages accessible to unauthenticated users
If the ThemeREX M.Williamson theme is installed, has unsanitized include/require statements using user-controlled parameters, and those parameters are accessible via HTTP, the environment is 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 dataSanitize and validate all user-supplied input before use in include/require statements, implement whitelisting of allowed files, or upgrade to a patched version of the theme if available. Consider deploying a WAF rule to block directory traversal patterns (e.g., ../../) as an interim control.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28055 — 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-28055 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