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

CVE-2025-60074

HIGH · 7.5 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Processby Lazy Load Optimizer lazy-load-optimizer allows PHP Local File Inclusion.This issue affects Lazy Load Optimizer: from n/a through <= 1.4.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

This is a Local File Inclusion (LFI) vulnerability in the Lazy Load Optimizer WordPress plugin. The vulnerability stems from improper validation of user-supplied input used in PHP include/require statements, allowing attackers to manipulate file paths and potentially read sensitive server files or achieve code execution.

MitigationUpgrade Lazy Load Optimizer to the latest patched version. If no patch is available, disable the plugin immediately and review server configurations to restrict file access paths.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Verify Lazy Load Optimizer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Lazy Load Optimizer' in the list. Alternatively, check the /wp-content/plugins/ directory for a lazy-load-optimizer folder.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, find Lazy Load Optimizer in Plugins > Installed Plugins and note the version number displayed below the plugin name. If not visible in admin, check the main plugin file (lazy-load-optimizer.php) in /wp-content/plugins/lazy-load-optimizer/ for the 'Version' header comment.
    Affected if The version cannot be determined or is older than the patched version
  3. Check for accessible file inclusion endpoints
    Inspect the plugin source code files (particularly PHP files in /wp-content/plugins/lazy-load-optimizer/) for code that uses include, require, include_once, or require_once with variables derived from $_GET, $_POST, or $_REQUEST parameters.
    Affected if The plugin contains file inclusion logic that processes user-supplied input without proper sanitization
  4. Review access logs for suspicious include/require requests
    Examine web server access logs (Apache access.log, Nginx access.log) for requests to the Lazy Load Optimizer plugin that contain file path traversal patterns such as ../, ..\, or absolute paths in query parameters.
    Affected if Log entries show requests to the plugin with path manipulation attempts

The environment is affected if Lazy Load Optimizer plugin is installed, the version is older than the patched version, and the plugin contains file inclusion logic that processes unsanitized user 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Lazy Load Optimizer to the latest patched version. If no patch is available, disable the plugin immediately and review server configurations to restrict file access paths.

Recommended fix Moderate confidence

Update to the latest available version of Lazy Load Optimizer (version 1.4.8 or higher if released)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Lazy Load Optimizer plugin
  4. Check if an update is available (compare current version to latest available version)
  5. If update available, click 'Update Now' to install the latest patched version
  6. After updating, verify the plugin is functioning correctly on the frontend

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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