CVE-2026-28093
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 Ozisti ozisti allows PHP Local File Inclusion.This issue affects Ozisti: from n/a through <= 1.1.10.
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 Local File Inclusion (LFI) vulnerability exists in ThemeREX Ozisti plugin/theme (versions <= 1.1.10) where PHP include/require statements do not properly validate user-supplied input, allowing attackers to read sensitive files from the server filesystem.
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 ThemeREX Ozisti installationSearch the webroot for directories or files containing 'ozisti' or 'themerex' naming patterns. Common locations include wp-content/plugins/, themes/, or vendor directories.Affected if ThemeREX Ozisti plugin or theme is found in the environment
-
Locate version fileCheck for version information in the plugin/theme header (typically in main PHP file comments), readme.txt, plugin.json, or version.php within the Ozisti directory.Affected if Version is 1.1.10 or lower (or version cannot be determined but the product is present)
-
Find include/require usage with external inputSearch PHP files in the Ozisti installation for include, include_once, require, or require_once statements that use variables derived from $_GET, $_POST, $_REQUEST, or similar superglobals as the path parameter.Affected if User-controlled parameters are passed directly to include/require without validation
-
Verify parameter accessibilityTest whether the vulnerable parameter can be controlled via HTTP request parameters (GET/POST) to the affected endpoints.Affected if The path parameter is accessible via HTTP and can be manipulated to traverse directories
-
Confirm file read capabilityAttempt to include a known safe file (such as ../wp-config.php or /etc/passwd using directory traversal) through the vulnerable parameter to verify LFI exists.Affected if The server returns content from files outside the intended directory
Environment is affected if ThemeREX Ozisti version 1.1.10 or lower is installed AND the include/require parameter accepts user-supplied input that can be exploited for directory traversal.
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 dataImplement strict input validation using whitelist approaches for file inclusion paths, disable allow_url_include, and ensure all include/require statements sanitize path parameters before use.
- 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-28093 — 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-28093 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