CVE-2026-28052
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 Peter Mason petermason allows PHP Local File Inclusion.This issue affects Peter Mason: from n/a through <= 1.4.5.
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 confidencePHP Local File Inclusion vulnerability in the ThemeREX Peter Mason WordPress theme allows remote attackers to include arbitrary PHP files via improper validation of user-supplied input to include/require statements. This can lead 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
- 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 Peter Mason theme installationList contents of wp-content/themes/ directory or check WordPress admin under Appearance > Themes for a theme named Peter Mason, Peter Mason ThemeREX, or similarAffected if The ThemeREX Peter Mason theme folder exists in the themes directory
-
Identify theme versionOpen the theme's style.css file in wp-content/themes/[peter-mason-folder]/ and locate the 'Version:' header in the CSS comment block at the topAffected if Version number is present and can be compared to the fixed version (contact theme vendor for specific version)
-
Check for include/require with user inputSearch all PHP files in the theme folder for patterns like 'include($_', 'require($_', 'include_once($_', 'require_once($_' followed by $_GET, $_POST, $_REQUEST, or similar superglobalsAffected if Theme files contain include/require statements that directly use unsanitized user-supplied input
-
Verify vulnerable parameter handlingExamine identified include/require calls to confirm the user input parameter (e.g., '?file=', '?page=') is used in the file path without validation, sanitization, or allowlist checksAffected if User-controlled parameters are passed directly to file inclusion functions without validation or sanitization
-
Confirm theme is accessibleAttempt to access the site with a crafted parameter like '?file=../../wp-config.php' or similar to test if arbitrary file inclusion is possibleAffected if The vulnerability is exploitable and the site responds with file contents or errors revealing inclusion behavior
User is affected if the ThemeREX Peter Mason theme is installed and active, and theme PHP files contain include/require statements that use unsanitized user input from $_GET, $_POST, or $_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 dataUpdate Peter Mason theme to latest version if available, or disable/replace the theme if unmaintained. Implement strict input validation and allowlist-based file inclusion controls.
- 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-28052 — 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-28052 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