LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28068: WordPress Rhythmo theme <= 1.3.4 - Local File Inclusion vulnerability

Improper 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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28068 affects the WordPress Rhythmo theme from ThemeREX through version 1.3.4. It is a local file inclusion issue that may let an unauthenticated remote attacker make the site include unintended server files. The CVSS score is high, but attack complexity is marked high.

Executive priority

Treat this as a high-priority WordPress exposure check, especially for public-facing sites. Prioritize inventory first because only sites using the Rhythmo theme appear affected. Escalate remediation if any installation is version 1.3.4 or earlier, but do not assume active exploitation from the provided evidence.

Technical view

The issue is classified as CWE-98: improper control of a filename used in a PHP include/require statement. The CVE description says Rhythmo <= 1.3.4 allows PHP Local File Inclusion. CVSS 3.1 is 8.1: network reachable, no privileges, no user interaction, high impact to confidentiality, integrity, and availability, with high attack complexity.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Rhythmo theme at version 1.3.4 or earlier. The CVE metadata has an inconsistency: the description names <= 1.3.4, while the affected entry lists version "0" and default status "unaffected." Validate directly against installed theme versions.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked KEV. The vulnerability is remotely reachable and unauthenticated by CVSS, but high attack complexity suggests exploitation may require specific site conditions. No public exploit details are included in the provided sources.

Researcher notes

Key uncertainty is the affected-version metadata inconsistency between the narrative and structured affected record. The safest interpretation is to validate all Rhythmo deployments through 1.3.4. No patch version, exploit status, or detailed technical trigger is provided in the source bundle, so further vendor confirmation is needed.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Rhythmo theme.
  • Identify any Rhythmo installations at version 1.3.4 or earlier.
  • Check ThemeREX and Patchstack guidance for an update or official mitigation.
  • If no fix is available, consider disabling or replacing the affected theme.
  • Restrict administrative access and maintain tested backups for affected WordPress sites.

Validation and detection

  • Confirm the installed theme name is Rhythmo by ThemeREX.
  • Record the installed Rhythmo version for each WordPress site.
  • Compare versions against the reported affected range: <= 1.3.4.
  • Review web and PHP logs for unusual include-related errors or unexpected file access.
  • Track whether the site uses customizations that could complicate theme replacement.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28068 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-28068Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXRhythmorhythmo, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.