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

CVE-2026-32369

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 RadiusTheme Medilink-Core medilink-core allows PHP Local File Inclusion.This issue affects Medilink-Core: from n/a through < 2.0.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 · high confidence

A PHP Local File Inclusion vulnerability exists in RadiusTheme Medilink-Core (versions before 2.0.7) where improper control of filename parameters in include/require statements allows attackers to include arbitrary local PHP files, potentially leading to remote code execution.

MitigationUpdate Medilink-Core to version 2.0.7 or later to patch the file inclusion vulnerability. If immediate update is not possible, disable the plugin/theme until patched.

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. Confirm Medilink-Core installation
    Locate the Medilink-Core plugin or theme files in the WordPress wp-content/plugins or wp-content/themes directory. Check for a folder named 'medilink-core' or similar naming pattern from RadiusTheme.
    Affected if The plugin or theme is not present on the system
  2. Identify installed version
    Open the main plugin/theme file (usually medilink-core.php or functions.php) and locate the version defined in the header comment or version constant. Alternatively, check the plugin metadata via WordPress admin plugin list or theme details.
    Affected if Version is present and is below 2.0.7 (e.g., 2.0.6, 2.0.5, 1.x, etc.)
  3. Locate vulnerable include/require statements
    Search the Medilink-Core source files for include, include_once, require, or require_once statements that use variable parameters without sanitization, such as include($file) or require($path . $_GET['file']). Look for dynamic file inclusion patterns.
    Affected if Dynamic include/require statements using unsanitized user input are found in the codebase
  4. Test vulnerable parameter access
    If dynamic file inclusion code is found, attempt to access the suspected endpoint with a benign path traversal attempt (e.g., ?file=../../../../wp-config.php) to confirm the parameter is accepted and processed by the application.
    Affected if The parameter is accepted and the application attempts to include the specified file, demonstrating the LFI vulnerability

The environment is affected if Medilink-Core is installed with a version lower than 2.0.7 AND the vulnerable dynamic file inclusion code path is accessible to attackers.

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 Medilink-Core to version 2.0.7 or later to patch the file inclusion vulnerability. If immediate update is not possible, disable the plugin/theme until patched.

Recommended fix Moderate confidence

RadiusTheme Medilink-Core version 2.0.7

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the Medilink-Core plugin by RadiusTheme.
  4. 4. Check the current installed version to confirm it is below 2.0.7.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.0.7.
  6. 6. If no automatic update appears, manually download version 2.0.7 from a trusted source and upload it via Plugins > Add New > Upload Plugin.
  7. 7. Verify the plugin updated successfully and test site functionality.
  8. 8. Monitor for any security-related plugin updates and apply them promptly.
Caveat Review plugin changelog for any configuration or feature changes between your current version and 2.0.7 before upgrading

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-32369 — 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-32369 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