dbcve.org
MediclinicWordPress extension · Qodeinteractive

CVE-2025-49295

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-09
Fix available
A fix is available. Upgrade to 2.2 or later.
See remediation →
100/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
Path Traversal: '.../...//' vulnerability in Mikado-Themes MediClinic mediclinic allows PHP Local File Inclusion.This issue affects MediClinic: from n/a through <= 2.1.

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 path traversal vulnerability using the '.../...//' pattern in Mikado-Themes MediClinic (versions up to 2.1) allows unauthenticated attackers to perform PHP Local File Inclusion (LFI), potentially leading to remote code execution by including and executing arbitrary PHP files on the server.

MitigationImplement strict input validation using realpath() to resolve and validate that file paths remain within allowed directories; if available, upgrade to a patched version of MediClinic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MediclinicWordPress extension
Affected:< 2.2

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

CVSS:3.1/AV:N/AC:L/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 MediClinic theme is installed
    Check your web application for the presence of MediClinic theme files by looking for theme-related directories or version files in your WordPress or PHP application installation
    Affected if The MediClinic theme by Qodeinteractive is present in the environment
  2. Identify installed version
    Locate the theme version file (commonly style.css in theme root or a version.php file) and read the declared version number
    Affected if The installed version is less than 2.2 (versions up to and including 2.1 are affected)
  3. Find file inclusion functionality
    Search PHP source files for functions that include, require, or include_once files with user-controlled input (common patterns: include($_GET['file'], require($_REQUEST['template'])
    Affected if The theme contains PHP files that dynamically include files based on request parameters without proper validation
  4. Test path traversal in accessible parameters
    If dynamic file inclusion is found, test the '.../...//' pattern (URL-encoded as %2e%2e%2f%2e%2e%2f%2e%2e%2f) in suspected file parameters to see if directory traversal is possible
    Affected if The application allows traversing outside the intended directory using the '.../...//' pattern in file include parameters

Your environment is affected if MediClinic theme version is below 2.2 and your server executes PHP files from paths controllable via the path traversal pattern in file inclusion functions.

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
Upgrade available Upgrade to 2.2 or later
Fixed in 2.2
Interim mitigation

Implement strict input validation using realpath() to resolve and validate that file paths remain within allowed directories; if available, upgrade to a patched version of MediClinic.

Recommended fix Moderate confidence

MediClinic version 2.2 or later

  1. 1. Back up your entire WordPress installation, including the database and all files
  2. 2. Download MediClinic theme version 2.2 or later from the official source (Mikado-Themes/ThemeForest)
  3. 3. Navigate to WordPress Admin Dashboard > Appearance > Themes
  4. 4. Deactivate the current vulnerable MediClinic theme
  5. 5. Delete the old MediClinic theme files
  6. 6. Upload and install the new MediClinic theme version 2.2+
  7. 7. Reactivate the MediClinic theme
  8. 8. Verify the theme is running version 2.2 or later by checking the theme documentation/about page
Caveat Review theme changelog for any default setting changes or template modifications that may affect child theme customizations

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

Fix this in Mediclinic 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 the upgrade done

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-2025-49295 — 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-2025-49295 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