CVE-2026-28095
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 Marcell marcell allows PHP Local File Inclusion.This issue affects Marcell: from n/a through <= 1.2.14.
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 confidenceThe ThemeREX Marcell WordPress theme (versions up to 1.2.14) contains a PHP Local File Inclusion (LFI) vulnerability where improper control of filename parameters in include/require statements allows attackers to include arbitrary local PHP files, potentially leading 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 ThemeREX Marcell theme is installedAccess WordPress admin, go to Appearance > Themes, and verify whether the ThemeREX Marcell theme is present and activeAffected if The ThemeREX Marcell theme is installed and active on the WordPress site
-
Identify the installed theme versionLocate the theme directory at wp-content/themes/marcell/ and open style.css to read the Version header, or view theme details in the WordPress admin theme listAffected if The installed version matches or falls within the known vulnerable version range
-
Identify vulnerable PHP include/require code pathsSearch the theme directory for PHP files containing include(), require(), include_once(), or require_once() statements that use REQUEST parameters, GET parameters, or unvalidated variables in file pathsAffected if The theme contains PHP files with include/require statements that process unsanitized user input for file paths
-
Check if vulnerable parameters are accessibleExamine the theme code to determine which URL parameters control the file inclusion, then verify these parameters can be reached from the frontend without authenticationAffected if The vulnerable file inclusion parameters are exposed and accessible to unauthenticated users
-
Compare against affected version rangeDocument the installed version and compare it against the known affected version ranges provided in vulnerability documentationAffected if The installed version is within the affected range and no security patch has been applied
A site is affected if it runs the ThemeREX Marcell theme with an unpatched version that contains the LFI vulnerability in its PHP include/require code paths.
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 ThemeREX Marcell to the latest patched version. As a temporary measure, implement strict input validation on all file inclusion parameters and consider deploying a WAF to block malicious file inclusion attempts.
- 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-28095 — 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-28095 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