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

CVE-2025-67920

HIGH · 8.1 CVSS v3.1 Published 2026-01-08
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 Elated-Themes Neo Ocular neoocular allows PHP Local File Inclusion.This issue affects Neo Ocular: from n/a through < 1.2.

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

Local File Inclusion vulnerability in Neo Ocular theme allows attackers to manipulate filename parameters in PHP include/require statements to include and execute arbitrary PHP files from the server file system, potentially leading to code execution.

MitigationUpgrade to Neo Ocular version 1.2 or later; alternatively, implement strict input validation on file inclusion parameters and disable allow_url_include in PHP configuration.

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. Identify Neo Ocular theme installation
    Search for Neo Ocular theme files in your web application's theme or template directory. Look for directories or files containing 'neo-ocular', 'neo_ocular', or 'neoocular' in the name.
    Affected if Neo Ocular theme files are found in the environment
  2. Determine Neo Ocular version
    Locate the version file, changelog, or theme declaration file (such as theme.json, info.xml, or a version.php) within the Neo Ocular theme directory. Read the declared version number.
    Affected if The installed version is earlier than 1.2 or the version cannot be determined
  3. Inspect PHP include/require usage
    Search within Neo Ocular theme PHP files for include, include_once, require, or require_once statements that use variables or parameters for the filename. Look for patterns where user input or request parameters feed into these file inclusion functions.
    Affected if Vulnerable include/require patterns using dynamic filename parameters are found in the theme PHP files
  4. Check for directory traversal in parameters
    Examine how filename parameters are handled. Look for code that concatenates user input into file paths without sanitization, allowing paths like ../../ to traverse directories.
    Affected if Filename parameters accept unsanitized input that could enable directory traversal (../../) or arbitrary file paths
  5. Verify parameter accessibility
    Determine if the vulnerable filename parameter is accessible via HTTP request (GET/POST parameters). Check if the parameter is exposed through URL query strings or form inputs.
    Affected if The vulnerable filename parameter is accessible via HTTP requests to the application

The environment is affected if Neo Ocular theme is installed with a version earlier than 1.2 and contains PHP include/require statements using unsanitized filename parameters controllable via HTTP requests.

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 to Neo Ocular version 1.2 or later; alternatively, implement strict input validation on file inclusion parameters and disable allow_url_include in PHP configuration.

Recommended fix Moderate confidence

Neo Ocular version 1.2

  1. 1. Backup the current website files and database before making any changes.
  2. 2. Download Neo Ocular theme version 1.2 from the official Elated-Themes source or theme repository.
  3. 3. Navigate to WordPress admin dashboard > Appearance > Themes.
  4. 4. Deactivate the current Neo Ocular theme or replace it with another theme temporarily.
  5. 5. Upload and install Neo Ocular version 1.2.
  6. 6. Activate Neo Ocular version 1.2.
  7. 7. Verify the website functionality is intact after the upgrade.
  8. 8. Confirm the LFI vulnerability is resolved by testing that arbitrary file paths can no longer be included via URL parameters.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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