CVE-2026-28011
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 Yottis yottis allows PHP Local File Inclusion.This issue affects Yottis: from n/a through <= 1.0.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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the ThemeREX Yottis WordPress theme. The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file path parameters to include arbitrary PHP files from the server's 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 Yottis theme installationCheck your WordPress theme directory (wp-content/themes/) for a folder named 'yottis' or 'trx_yottis'. Use file manager or command: ls wp-content/themes/ | grep -i yottisAffected if The yottis theme folder exists in the WordPress themes directory
-
Determine installed Yottis theme versionOpen the style.css file in the theme folder and look for the 'Version:' header, or check theme.json. Alternatively, in WordPress admin go to Appearance > Themes and click on the Yottis theme to view its details.Affected if The reported version is 1.0.10 or lower, or no version is displayed (older unversioned release)
-
Identify vulnerable LFI code patternsSearch theme PHP files for include/require statements that use variables without sanitization, especially those using $_GET, $_POST, or $_REQUEST parameters. Example grep: grep -r '\$_(GET|POST|REQUEST)' wp-content/themes/yottis/ | grep -i 'include\|require'Affected if PHP include/require statements directly use unsanitized user input from URL parameters
-
Check PHP configuration for allow_url_includeCreate a PHP file with <?php phpinfo(); ?> and access it in a browser, or run: php -i | grep allow_url_include. Check the value in php.ini or .user.ini.Affected if allow_url_include is set to On (this compounds the LFI into remote file inclusion potential)
-
Inspect web server access logs for LFI attemptsReview web server logs (Apache access.log, Nginx access.log) for requests containing patterns like ../, ..\, /etc/passwd, or file paths in URL parameters targeting the theme. Example: grep -E '\.\./|\.\.\\' /var/log/apache2/access.logAffected if Recent or historical requests contain directory traversal patterns or suspicious file inclusion attempts to theme files
Your environment is affected if the Yottis theme version 1.0.10 or lower is installed and contains PHP include/require statements that use unsanitized user input from URL 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 dataDisable or remove the affected Yottis theme version until a patched version is available; implement web application firewall rules to block directory traversal patterns (e.g., ../) in request parameters.
- 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-28011 — 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-28011 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