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

CVE-2025-69061

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 MoveMe moveme allows PHP Local File Inclusion.This issue affects MoveMe: from n/a through <= 1.2.15.

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 (LFI) vulnerability exists in the AncoraThemes MoveMe theme. The vulnerability allows attackers to manipulate file path parameters in include/require statements to read arbitrary files on the server, potentially exposing sensitive configuration files, source code, or system files.

MitigationUpdate the MoveMe theme to a patched version once released. Until then, implement strict input validation on all file inclusion parameters to prevent path traversal, disable allow_url_include, and review code for insecure use of include/require with user-supplied input.

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 MoveMe theme is installed
    Locate the theme directory - typically in wp-content/themes/moveme (WordPress) or your application's theme folder. Check for existence of style.css, functions.php, or theme configuration files bearing the MoveMe or AncoraThemes name.
    Affected if MoveMe theme files are present in the environment
  2. Identify the installed theme version
    Open the theme's style.css file (usually at /wp-content/themes/moveme/style.css) and look for the 'Version:' declaration in the header comments. Alternatively, check version.php or theme.json if present.
    Affected if Version is lower than 1.2.16 or the version cannot be determined (indicating an older or unpatched release)
  3. Locate PHP files using dynamic file inclusion
    Search the theme directory for PHP files containing 'include(' or 'require(' statements with variable arguments, e.g., include($something), require($_GET[...]). Use grep: grep -rn '\$.*include\|\$.*require' /path/to/moveme/
    Affected if Dynamic include/require statements using unsanitized variables are found in theme PHP files
  4. Identify input sources feeding file inclusion functions
    Examine identified vulnerable include/require code paths. Trace variable sources: check if parameters from $_GET, $_POST, or other user-controllable arrays are passed directly to file inclusion functions without validation.
    Affected if User-supplied input (GET/POST parameters, cookies, or request variables) flows directly to include/require without sanitization or whitelist validation
  5. Test for path traversal in accessible endpoints
    If theme exposes parameters that might control file paths (common in plugins or shortcodes), attempt a safe read test using a known non-sensitive file path such as ../../../../../../etc/passwd in an affected parameter. Only perform this in non-production environments.
    Affected if The application returns contents of files outside the theme directory based on user-controlled path parameters

The environment is affected if MoveMe theme is installed with a version below 1.2.16 AND the theme contains PHP code that includes/requires files using unsanitized user-supplied 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.

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

Update the MoveMe theme to a patched version once released. Until then, implement strict input validation on all file inclusion parameters to prevent path traversal, disable allow_url_include, and review code for insecure use of include/require with user-supplied input.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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