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

CVE-2025-69076

HIGH · 8.1 CVSS v3.1 Published 2026-01-22
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 AncoraThemes Modern Housewife modernhousewife allows PHP Local File Inclusion.This issue affects Modern Housewife: from n/a through <= 1.0.12.

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 vulnerability exists in the Modern Housewife theme where user-supplied input is used in include/require statements without proper validation. Attackers can manipulate file path parameters to read sensitive local files from the server, potentially exposing configuration files, credentials, or source code.

MitigationImplement strict whitelist-based input validation on file path parameters to prevent path traversal sequences (e.g., ../) and restrict included files to an allowed directory. Alternatively, refactor to avoid dynamic file inclusion entirely.

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 Modern Housewife theme is installed
    Search your web root for theme files named 'modern-housewife', 'modernhousewife', or check your CMS theme directory for this specific theme. Look for style.css or theme.xml files containing the theme name.
    Affected if The theme files exist in your web application directory tree.
  2. Locate PHP files with dynamic file inclusion
    Search the theme directory recursively for PHP files containing 'include' or 'require' statements that use variables, such as 'include($', 'require($', 'include_once($', or 'require_once($' without hardcoded paths.
    Affected if PHP files use variable-based include/require statements that could accept user input.
  3. Identify file path parameters in the codebase
    Review the PHP files found in the previous step. Look for parameters passed via GET or POST requests (e.g., $_GET['file'], $_POST['path']) that are used within include/require statements.
    Affected if URL parameters or form inputs are directly used in file inclusion functions without sanitization.
  4. Check for input validation on file path parameters
    Examine the PHP files handling file inclusion. Verify whether the code implements whitelist validation, basename(), or realpath() to restrict included files to allowed directories. Look for filtering of '../' sequences.
    Affected if No input validation exists, or path traversal sequences like '../' are not filtered before being used in include/require statements.
  5. Test for path traversal vulnerability (if authorized)
    If you have authorization to perform security testing, attempt to include a known local file using path traversal (e.g., ?file=../../../../etc/passwd) through any identified file path parameters.
    Affected if The application returns content from files outside the intended directory, confirming the LFI vulnerability.

You are affected if the Modern Housewife theme is installed and contains PHP files that use user-supplied input in include/require statements without proper path validation or whitelist filtering.

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

Implement strict whitelist-based input validation on file path parameters to prevent path traversal sequences (e.g., ../) and restrict included files to an allowed directory. Alternatively, refactor to avoid dynamic file inclusion entirely.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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