dbcve.org
WilmerWordPress extension · Qodeinteractive

CVE-2025-67515

HIGH · 8.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 3.5 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Mikado-Themes Wilmër wilmer allows PHP Local File Inclusion.This issue affects Wilmër: from n/a through < 3.5.

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 Local File Inclusion (LFI) vulnerability exists in the Mikado-Themes Wilmër WordPress theme. The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file paths and potentially read sensitive local files from the server. This affects all versions prior to 3.5.

MitigationUpdate the Wilmër theme to version 3.5 or later. Additionally, ensure PHP configuration disables allow_url_fopen and allow_url_include, and implement proper input validation on any file path parameters.

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
WilmerWordPress extension
Affected:< 3.5

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

CVSS:3.1/AV:N/AC:L/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. Locate the Wilmër theme installation
    Search your web server's document root for directories named 'wilmer' or 'Wilmër' - typically found in wp-content/themes/ for WordPress installations. Check for a style.css file with the theme name header.
    Affected if The theme directory exists on the server and contains theme files.
  2. Determine the installed theme version
    Open the theme's style.css file (usually at wp-content/themes/wilmer/style.css) and locate the 'Version:' comment in the file header. Alternatively, check the theme's functions.php for a version constant or variable.
    Affected if The version is listed as less than 3.5 (e.g., 3.4, 3.3, 1.0, etc.).
  3. Identify PHP files with file inclusion functions
    Search all .php files within the wilmer theme directory for patterns like 'include(', 'require(', 'include_once(', 'require_once(' followed by variables (e.g., $_, GET, POST, or REQUEST). Use grep or a text editor to find these patterns.
    Affected if PHP files contain include/require statements using unsanitized variable parameters that could be manipulated via URL or form input.
  4. Inspect path parameters in theme PHP files
    Review the identified file inclusion code for parameters that accept user input (such as 'file', 'page', 'template', 'path', 'slug' in $_GET or $_REQUEST). Verify if these parameters are used directly in include/require without validation or sanitization.
    Affected if Parameters are used directly in file inclusion functions without sanitization functions like basename(), realpath(), or whitelist validation.

If the Wilmër theme version is installed and is below 3.5, and the theme contains file inclusion code that uses unsanitized user-controlled parameters, the environment is vulnerable to CVE-2025-67515.

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

Update the Wilmër theme to version 3.5 or later. Additionally, ensure PHP configuration disables allow_url_fopen and allow_url_include, and implement proper input validation on any file path parameters.

Recommended fix Moderate confidence

Wilmer theme version 3.5

  1. 1. Check the currently installed Wilmer theme version in your WordPress installation (typically under Appearance > Themes)
  2. 2. Download Wilmer theme version 3.5 or later from the official source (Mikado-Themes/MikadoInc)
  3. 3. Before upgrading, backup your current theme files and website database
  4. 4. Upload and install the Wilmer 3.5 theme via WordPress admin panel (Appearance > Themes > Add New > Upload) or via FTP/SFTP to wp-content/themes/
  5. 5. After installation, verify the new version is active and the website functions correctly
  6. 6. Clear any site caches if applicable

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

Fix this in Wilmer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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