dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-28107

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

The ThemeREX Muzicon plugin/theme for WordPress contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated and used in include/require statements, allowing attackers to include arbitrary PHP files from the local filesystem.

MitigationImplement strict input validation with whitelist checking for file paths, avoid using user input directly in include/require statements, and update to a patched version if available.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ThemeREX Muzicon installation
    Search the WordPress plugins directory (wp-content/plugins) and themes directory (wp-content/themes) for a folder named 'muzicon' or 'trx_muzicon'. Alternatively, check the WordPress admin plugin/theme list.
    Affected if The ThemeREX Muzicon plugin or theme is present in the WordPress installation
  2. Identify installed version
    Check the main plugin/theme file (e.g., index.php, style.css, or a main muzicon.php file) inside the muzicon directory for a version comment or defined version constant. Also check readme.txt if present.
    Affected if The installed version cannot be determined or is unknown, making it difficult to confirm patch status
  3. Locate include/require statements using user input
    Search the plugin/theme files for include, require, include_once, or require_once statements that use variables (e.g., include($file), require($_GET['param'])) without proper sanitization. Common vulnerable patterns involve 'file', 'path', 'page', 'slug', or 'template' parameters.
    Affected if Code is found that directly uses request parameters or user-controllable variables in include/require statements without validation such as basename(), realpath(), or whitelist checking
  4. Test for LFI via HTTP requests
    If the vulnerable parameter is identified, attempt a benign LFI test by including a known file (e.g., ../../../../wp-config.php) as a parameter value. Observe if the application attempts to load the file or returns an error revealing the path.
    Affected if The application returns file contents or error messages that disclose the full filesystem path when a path traversal sequence is provided in the parameter
  5. Review .htaccess or access controls
    Check if the muzicon directory or vulnerable script has any .htaccess restrictions or if the web server configuration limits direct access to the vulnerable file.
    Affected if No access restrictions exist, allowing unauthenticated users to directly request the vulnerable script

The environment is affected if the ThemeREX Muzicon plugin/theme is installed and contains code that uses unsanitized user input in include/require statements, or if direct access to any such vulnerable file is possible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation with whitelist checking for file paths, avoid using user input directly in include/require statements, and update to a patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28107 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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