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

CVE-2026-32426

HIGH · 7.5 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 themelexus Medilazar Core medilazar-core allows PHP Local File Inclusion.This issue affects Medilazar Core: from n/a through < 1.4.7.

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

A Local File Inclusion (LFI) vulnerability exists in the themelexus Medilazar Core theme where user-supplied input is not properly validated before being used in PHP include/require statements. This allows attackers to potentially read sensitive files from the server filesystem via path traversal attacks.

MitigationUpdate Medilazar Core to version 1.4.7 or later. If immediate update is not possible, audit code for unsafe include/require usage and implement strict input validation to restrict file paths to expected directories.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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. Identify Medilazar Core theme version
    Check the theme's version file, typically in style.css or theme.json within the theme directory, or look for a version constant in the main theme PHP files
    Affected if Version is below 1.4.7 (prior to the fix)
  2. Locate PHP include/require usage with dynamic input
    Search theme PHP files for patterns like include($_GET, require($_POST, or similar constructs where user-supplied parameters are used directly in file inclusion functions
    Affected if Dynamic file inclusion using unvalidated user input is found in the codebase
  3. Identify path traversal patterns in request handling
    Review PHP files that handle URL parameters (e.g., $_GET, $_REQUEST) and pass them to include/require statements without sanitization, looking for patterns like '../' or direct parameter usage
    Affected if User-controlled parameters flow directly to include/require without validation or path sanitization
  4. Check input validation on file path handlers
    Examine any code that processes file path parameters (commonly named 'page', 'file', 'template', 'path', or similar) to determine if realpath(), basename(), or allowlist validation is performed
    Affected if No input validation or allowlisting is implemented on file path parameters used in inclusions
  5. Verify accessible endpoints
    Identify which PHP endpoints accept user input that could reach the vulnerable include/require logic by testing or reviewing the application's routing
    Affected if User-accessible endpoints can trigger the vulnerable include/require code path

The environment is affected if Medilazar Core theme version is below 1.4.7 AND the theme contains PHP code where user-supplied input flows directly to include/require statements without validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Medilazar Core to version 1.4.7 or later. If immediate update is not possible, audit code for unsafe include/require usage and implement strict input validation to restrict file paths to expected directories.

Recommended fix High confidence

1.4.7

  1. Identify the themelexus Medilazar Core plugin or theme installation in your environment
  2. Upgrade Medilazar Core to version 1.4.7 or later
  3. Verify the upgrade was successful by checking the installed version
  4. Test that the application functions normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32426 — 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-32426 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