dbcve.org
MedizinWordPress extension · Thememove

CVE-2025-59555

HIGH · 8.1 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to 1.9.7 or later.
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 ThemeMove Medizin medizin allows PHP Local File Inclusion.This issue affects Medizin: from n/a through < 1.9.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 PHP Local File Inclusion (LFI) vulnerability in ThemeMove Medizin theme allows attackers to include arbitrary local PHP files through unsanitized input to include/require statements, potentially leading to remote code execution. The vulnerability stems from improper control of filenames used in PHP include/require functions.

MitigationUpgrade to Medizin version 1.9.7 or later which contains the patch for this LFI vulnerability. If immediate patching is not possible, implement input validation and path traversal checks on all user-supplied parameters used in include/require statements.

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
MedizinWordPress extension
Affected:< 1.9.7

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. Identify installed Medizin theme version
    Locate the theme's version information - typically found in the theme's style.css header (WordPress themes), a version.php file, or in the theme's main configuration file. Check the theme directory at wp-content/themes/medizin/
    Affected if The installed version is lower than 1.9.7 (e.g., 1.9.6, 1.9.5, 1.0, etc.)
  2. Locate PHP files handling include/require statements
    Search the Medizin theme directory for PHP files containing include, require, include_once, or require_once statements. Focus on files that process user-supplied parameters (look for $_GET, $_POST, or similar superglobal variables passed to these functions)
    Affected if The theme contains PHP files that use include/require with parameters derived from user input without proper sanitization
  3. Inspect include/require parameter sources
    Examine each PHP file found in the previous step. Trace back the source of each parameter used in include/require calls. Look for patterns like: include($_GET['file']); or require($variable); where the variable originates from URL or form input
    Affected if Any include/require statement uses a filename or path variable that directly or indirectly receives input from $_GET, $_POST, or other user-controllable sources without validation
  4. Verify input validation on vulnerable files
    If include/require statements with user input are found, examine whether the code performs validation such as: allowlists of permitted files, removal of path traversal sequences (../, ..\), sanitization of special characters, or use of basename() function
    Affected if No input validation, sanitization, or path traversal protection exists on parameters used in include/require functions
  5. Test for path traversal vulnerability
    If vulnerable include/require code is identified, attempt to access known local files via the suspected parameter (e.g., adding ../../../../../../etc/passwd to the parameter value in a test/non-production environment)
    Affected if The application returns content from arbitrary local files based on user-supplied input in include/require statements

The environment is affected if the Medizin theme version is below 1.9.7 AND the theme contains PHP files with include/require statements that use unsanitized user-supplied input.

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 1.9.7 or later
Fixed in 1.9.7
Interim mitigation

Upgrade to Medizin version 1.9.7 or later which contains the patch for this LFI vulnerability. If immediate patching is not possible, implement input validation and path traversal checks on all user-supplied parameters used in include/require statements.

Recommended fix Moderate confidence

Medizin 1.9.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. If the Medizin theme is active, activate a different theme temporarily
  4. Delete the vulnerable Medizin theme
  5. Upload and install the Medizin theme version 1.9.7 or later from a trusted source
  6. Activate the updated Medizin theme
  7. Verify the theme is functioning correctly
  8. Check that all customizations and settings are intact

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

Fix this in Medizin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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