CVE-2026-28046
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 Law Office law-office allows PHP Local File Inclusion.This issue affects Law Office: from n/a through <= 3.3.0.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the ThemeREX Law Office WordPress theme. The vulnerability allows attackers to include arbitrary files from the server due to improper control of filename parameters in PHP include/require statements, potentially exposing sensitive system 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
- 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 ThemeREX Law Office theme is installedNavigate to wp-content/themes/ directory or check via WordPress admin under Appearance > Themes. Look for a theme folder named 'law-office' or similar ThemeREX theme directory.Affected if The ThemeREX Law Office theme is present in the WordPress installation.
-
Determine the installed theme versionCheck the style.css file within the theme directory for the 'Version:' header, or access it via WordPress admin theme details panel.Affected if The theme version is lower than the patched version (version comparison needed against known fixed release).
-
Locate vulnerable PHP include filesSearch theme PHP files for include/require statements that use variables in filename parameters without sanitization. Common patterns: include($_GET['file']), include($path . $_GET['template']). Look in main theme files like functions.php or custom template files.Affected if Theme files contain include/require statements using unsanitized user input (e.g., $_GET, $_POST) in the file path.
-
Check for accessible vulnerable parametersIf vulnerable code is found, test accessing common LFI parameters via HTTP requests to the site. Typical parameter names include 'file', 'template', 'path', 'page', 'include'.Affected if The vulnerable parameter is accessible via HTTP and accepts path traversal input without being blocked.
-
Verify PHP configuration settingsCheck phpinfo() or php configuration for allow_url_include setting. Also verify open_basedir restrictions if configured.Affected if PHP allow_url_include is enabled (increases severity) or no open_basedir restrictions are in place to limit file access.
A user is affected if the ThemeREX Law Office theme is installed with a vulnerable version containing unsanitized include/require statements and the vulnerable parameter is accessible without proper access controls.
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 the theme to the latest patched version. If no update is available, disable the theme and implement WAF rules to block directory traversal patterns (../, etc.). Additionally, ensure PHP configuration has allow_url_include disabled and consider restricting file access permissions.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28046 — 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-28046 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