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

CVE-2025-67941

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 Elated-Themes The Aisle theaisle allows PHP Local File Inclusion.This issue affects The Aisle: from n/a through < 2.9.1.

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 Aisle WordPress theme (versions before 2.9.1) contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in include/require statements. This allows attackers to include arbitrary local PHP files, potentially leading to remote code execution if they can control included files or leverage log poisoning techniques.

MitigationUpgrade to The Aisle version 2.9.1 or later. Until then, disable the affected theme or implement web application firewall rules to block directory traversal patterns (e.g., ../) in URL parameters.

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. Check installed Aisle theme version
    In WordPress admin, go to Appearance > Themes and check the Aisle theme version, or inspect the style.css file in wp-content/themes/aisle/ for the 'Version' header
    Affected if Version is lower than 2.9.1 (e.g., 2.9.0, 2.8.x, etc.)
  2. Inspect theme PHP files for unsafe file inclusion
    Search theme files (especially functions.php, template files) for include, require, include_once, or require_once statements that use variables without sanitization, particularly $_GET, $_POST, or $_REQUEST parameters
    Affected if Found include/require statements using raw user input without validation (e.g., include($_GET['template']);)
  3. Identify URL parameters that control file inclusion
    Review theme code for parameters like 'file', 'page', 'template', 'path', or 'slug' passed to include/require functions, then test if these parameters accept directory traversal sequences
    Affected if Theme exposes a parameter that can be manipulated to include arbitrary local PHP files using ../ patterns
  4. Check web server access logs for exploitation attempts
    Review Apache/nginx access logs in /var/log/ for requests to the theme containing ../ sequences or common LFI patterns like ../../../../etc/passwd
    Affected if Log entries show directory traversal attempts targeting the Aisle theme
  5. Verify if PHP allow_url_include is enabled
    Check php.ini for allow_url_include = On (though this vulnerability is LFI not RFI, this affects severity)
    Affected if allow_url_include is enabled and theme accepts external URLs in inclusion parameters

You are affected if the Aisle theme version is below 2.9.1 AND the theme exposes a file inclusion mechanism using unsanitized user input that can be exploited via directory traversal.

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 The Aisle version 2.9.1 or later. Until then, disable the affected theme or implement web application firewall rules to block directory traversal patterns (e.g., ../) in URL parameters.

Recommended fix Moderate confidence

2.9.1 or later

  1. 1. Backup the entire WordPress site before making any changes
  2. 2. Update The Aisle theme to version 2.9.1 or later through WordPress admin dashboard (Appearance > Themes)
  3. 3. If automatic update is not available, manually download the latest version from the theme vendor
  4. 4. Verify the update was successful by checking the theme version number
  5. 5. Test the affected functionality to confirm the vulnerability is remediated

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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