CVE-2026-28068
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 Rhythmo rhythmo allows PHP Local File Inclusion.This issue affects Rhythmo: from n/a through <= 1.3.4.
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 confidencePHP Local File Inclusion vulnerability in ThemeREX Rhythmo theme allows attackers to manipulate include/require statements with malicious file paths, potentially enabling remote code execution by including arbitrary PHP files from the server filesystem or remote sources.
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 Rhythmo theme installationSearch the web server filesystem for theme files named 'rhythmo', 'themerex', or check wp-content/themes for a Rhythmo theme folderAffected if The ThemeREX Rhythmo theme folder exists on the server
-
Identify theme versionCheck theme style.css header, functions.php, or theme.xml for a Version: field; compare against any known version rangesAffected if Installed version matches or predates any vulnerable version of the Rhythmo theme
-
Locate include/require statements using user inputGrep the theme PHP files for patterns like $_GET, $_POST, or $_REQUEST being used inside include, require, include_once, or require_once functionsAffected if Code references user-controlled parameters in dynamic include/require paths
-
Identify vulnerable URL parametersReview the parameters passed to include/require and test if they can be manipulated via HTTP requests (GET/POST)Affected if URL parameters directly influence the file path in include/require without sanitization
-
Check PHP allow_url_include settingInspect php.ini or run phpinfo() to check if allow_url_include is enabledAffected if allow_url_include is On, allowing remote file inclusion via URLs in include statements
A system is affected if it runs the ThemeREX Rhythmo theme with code that uses unsanitized user input in include/require statements, particularly with allow_url_include enabled.
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 and allowlist-based filtering on any parameters used in include/require statements; disable allow_url_include; upgrade to patched version when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28068 — 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-28068 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