CVE-2026-28054
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 Legal Stone legal-stone allows PHP Local File Inclusion.This issue affects Legal Stone: 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 confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the ThemeREX Legal Stone WordPress plugin. The vulnerability allows attackers to manipulate filename parameters in include/require statements to execute arbitrary PHP code by including malicious local 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 Legal Stone plugin is installedCheck the WordPress plugins directory at wp-content/plugins/ for a folder named 'legal-stone', 'themerex-legal-stone', or similar ThemeREX legal-related pluginAffected if The plugin folder exists in the WordPress plugins directory
-
Determine installed plugin versionOpen the main plugin PHP file (usually legal-stone.php or index.php inside the plugin folder) and look for a version comment at the top, or check the readme.txt file for the Version: fieldAffected if Unable to determine version or version is older than the patched release (version comparison required)
-
Locate file inclusion code in plugin PHP filesSearch plugin PHP files for include(), require(), include_once(), or require_once() statements that use dynamic variables such as $_GET, $_POST, or $_REQUEST as part of the file pathAffected if Dynamic file inclusion found without proper sanitization of user input parameters
-
Inspect filename parameter handlingExamine any PHP code handling 'file', 'filename', 'path', or similar parameters from user requests. Check if these parameters are used directly in include/require calls without validationAffected if Parameters from user input are used directly in file inclusion functions without sanitization or whitelisting
-
Check for directory traversal patterns in requestsReview server access logs for requests to the plugin that contain '../' or encoded traversal sequences (like %2e%2e%2f) in query parametersAffected if Such requests have been made to the site, indicating exploitation attempts
The environment is affected if the ThemeREX Legal Stone plugin is installed AND contains file inclusion code that uses unsanitized user-supplied input in include/require statements.
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 Legal Stone plugin to the latest version which should contain patched code with proper input validation/sanitization on file inclusion paths. If no update is available, implement web application firewall rules to block directory traversal patterns in request parameters.
- 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-28054 — 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-28054 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