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

CVE-2025-69339

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 don-themes Molla molla allows PHP Local File Inclusion.This issue affects Molla: from n/a through <= 1.5.16.

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

The Molla theme for PHP contains an improper control of filename for include/require statement vulnerability (CWE-98), allowing unauthenticated attackers to include arbitrary files via user-controlled input. This can lead to local file inclusion (LFI) and potentially remote code execution if the attacker can control included file paths or upload malicious files to the server.

MitigationUpgrade to a patched version of the Molla theme. If no patch is available, disable the affected component or implement strict input validation and allowlist controls on all file inclusion parameters to prevent path traversal and arbitrary file inclusion.

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
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. Confirm Molla theme is installed
    Search for theme files named 'molla' or containing 'Molla' in the theme header, typically found in wp-content/themes/ or similar web root directories.
    Affected if The Molla theme is present in the environment
  2. Identify the installed Molla theme version
    Check the style.css file in the Molla theme directory for the 'Version:' comment in the theme header, or check theme.json, or look for a version definition in the theme's main PHP file.
    Affected if The installed version matches any version known to be affected by CVE-2025-69339 (compare against vendor release notes)
  3. Locate include/require statements using user input
    Search the theme's PHP files for patterns like 'include($_GET', 'require($_POST', 'include($_REQUEST', or similar where superglobal arrays are passed directly to include/require functions without sanitization.
    Affected if Unsanitized user input (GET, POST, REQUEST, COOKIE) is used directly in include or require statements
  4. Verify file inclusion functions are reachable
    Examine the code flow around vulnerable include/require calls to determine if user-supplied parameters can reach these functions through HTTP requests without authentication or validation.
    Affected if The file inclusion functionality is accessible without requiring authentication or additional validation steps
  5. Check for known vulnerable file paths
    Inspect any PHP files in the Molla theme that handle file path parameters (e.g., parameters named 'file', 'path', 'template', 'page', 'slug') and trace whether these values flow to include/require without validation.
    Affected if Parameters accepting file paths can be manipulated to include arbitrary local or remote files

The environment is affected if the Molla theme is installed, uses a version within the affected range, and contains include/require statements that accept unsanitized user input which is accessible to attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the Molla theme. If no patch is available, disable the affected component or implement strict input validation and allowlist controls on all file inclusion parameters to prevent path traversal and arbitrary file inclusion.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-69339 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