LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28107: WordPress Muzicon theme <= 1.9.0 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX Muzicon muzicon allows PHP Local File Inclusion.This issue affects Muzicon: from n/a through <= 1.9.0.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-28107 affects the WordPress Muzicon theme from ThemeREX through version 1.9.0. It may let an unauthenticated remote attacker include local files through unsafe PHP include handling. That can threaten confidentiality, integrity, and availability. No cited source here confirms active exploitation or a fixed version.

Executive priority

Prioritize affected public WordPress sites because the vulnerability has high potential business impact and requires no login. Urgency is tempered by high attack complexity and no confirmed active exploitation in the provided sources. Validate exposure first, then follow vendor or Patchstack remediation guidance.

Technical view

The issue is classified as CWE-98: improper control of filenames in PHP include/require statements. The CVSS 3.1 score is 8.1 with network access, no privileges, no user interaction, high attack complexity, and high impact across CIA. The CVE description characterizes the outcome as PHP local file inclusion in Muzicon <= 1.9.0.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Muzicon theme at version 1.9.0 or earlier. The supplied affected-version data is somewhat inconsistent, so teams should verify installed theme name and version directly against vendor or Patchstack records.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation without user interaction, but high attack complexity. The source bundle does not identify public exploit code, in-the-wild exploitation, or CISA KEV listing. Treat internet-facing WordPress sites running affected versions as higher priority.

Researcher notes

The public data names Muzicon <= 1.9.0 and CWE-98, but does not provide a patched version, exploit details, or proof of exploitation. The source bundle’s affected-version structure appears incomplete or inconsistent, so rely on direct theme-version verification and updated vendor intelligence.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Muzicon theme.
  • Identify installed Muzicon versions and flag version 1.9.0 or earlier.
  • Check ThemeREX and Patchstack for fixed-version or mitigation guidance.
  • If no fix is available, consider disabling or replacing the theme.
  • Back up sites before theme changes or emergency remediation.

Validation and detection

  • Confirm whether Muzicon is installed on each WordPress site.
  • Record the exact theme version from trusted administrative sources.
  • Compare findings with the CVE and Patchstack affected-version statement.
  • Review web server and WordPress logs for unusual file-include related errors.
  • Document compensating controls if the theme cannot be immediately removed.
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-28107 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-28107Attack 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
ThemeREXMuziconmuzicon, 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.