dbcve.org
OptimizeWordPress extension · Qodeinteractive

CVE-2025-67935

HIGH · 8.1 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to 2.4 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 Mikado-Themes Optimize optimizewp allows PHP Local File Inclusion.This issue affects Optimize: from n/a through < 2.4.

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

The Optimize WordPress theme by Mikado-Themes contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without adequate sanitization. An attacker could potentially read sensitive local files or achieve code execution by manipulating the file path parameters.

MitigationUpdate the Optimize theme to version 2.4 or later which contains the patched code. If immediate update is not possible, disable the theme or implement web application firewall rules to block directory traversal patterns in URL 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
OptimizeWordPress extension
Affected:< 2.4

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. Locate the Optimize theme installation directory
    Check your WordPress themes directory (commonly wp-content/themes/) for a folder named 'optimize', 'mikado-optimize', or similar variants of the Optimize theme by Qodeinteractive.
    Affected if The theme folder is present on the server
  2. Identify the installed theme version
    Open the style.css file within the Optimize theme folder and locate the 'Version:' header in the file comment block, or check version.php if present in the theme root.
    Affected if The version listed is less than 2.4 (e.g., 2.3, 2.2, 1.x)
  3. Check for vulnerable include/require code patterns
    Search theme PHP files for include(), require(), include_once(), or require_once() statements that use variable parameters without sanitization, particularly those handling file path arguments from user input (e.g., $_GET, $_POST).
    Affected if Any PHP files contain dynamic file inclusion using unsanitized variables referencing request parameters
  4. Verify PHP execution in writable directories
    Review web server configuration and .htaccess rules in wp-content/uploads/ and other writable directories to confirm if PHP execution is blocked. Check for directives like 'php_flag engine off' or 'RemoveHandler .php' in those directories.
    Affected if PHP execution is allowed in directories where users can upload files

You are affected if the Optimize theme version is below 2.4 AND the theme contains vulnerable include/require code that uses unsanitized input from request parameters.

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.4 or later
Fixed in 2.4
Interim mitigation

Update the Optimize theme to version 2.4 or later which contains the patched code. If immediate update is not possible, disable the theme or implement web application firewall rules to block directory traversal patterns in URL parameters.

Recommended fix High confidence

Optimize version 2.4

  1. 1. Backup your entire WordPress installation including database and files before proceeding
  2. 2. Download the latest version of the Optimize theme (version 2.4 or later) from the official Mikado-Themes source or your theme provider
  3. 3. Navigate to Appearance > Themes in your WordPress admin dashboard
  4. 4. If possible, activate a different theme temporarily to deactivate Optimize
  5. 5. Delete the existing Optimize theme files
  6. 6. Upload and install the new Optimize theme version 2.4 or later
  7. 7. Reactivate the Optimize theme
  8. 8. Verify the theme is running version 2.4 or later in the theme settings
Caveat Review any custom child theme or customizations that may be affected by the upgrade; standard WordPress theme upgrade precautions apply

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

Fix this in Optimize Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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