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

CVE-2026-24609

HIGH · 7.5 CVSS v3.1 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 Laurent laurent allows PHP Local File Inclusion.This issue affects Laurent: from n/a through <= 3.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

Local File Inclusion (LFI) vulnerability in the Laurent WordPress theme allows attackers to include arbitrary local PHP files via improper control of filename parameters in include/require statements. The vulnerability stems from insufficient input validation on file inclusion functions, enabling path traversal attacks.

MitigationUpdate the Laurent theme to a patched version if available. If no patch exists, implement strict input validation and whitelist-based filtering on all file inclusion functions to prevent path traversal, or disable potentially dangerous include/require functionality.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 Laurent theme is installed
    Check the WordPress themes directory (wp-content/themes/) for the presence of a 'laurent' or 'Laurent' folder. Alternatively, query the WordPress database: SELECT theme FROM wp_themes WHERE name LIKE '%laurent%';
    Affected if The Laurent theme folder exists in the WordPress themes directory
  2. Locate the installed theme version
    Open the style.css file in the Laurent theme folder (wp-content/themes/laurent/style.css) and look for the 'Version:' header in the file comments, or check the theme's main PHP file for a version constant
    Affected if The version cannot be determined or is unknown - compare any found version against the vendor's release notes for patched versions
  3. Search for vulnerable include/require patterns
    Grep the Laurent theme files for dynamic include/require statements: grep -rn "include(\|require(\|include_once(\|require_once(" wp-content/themes/laurent/ - examine any that use variables or parameters without sanitization
    Affected if The theme code contains include/require statements that use variables or request parameters without validation (e.g., include($_GET['file']); or include($file);)
  4. Identify file parameter handling
    Search for $_GET, $_POST, or $_REQUEST usage in theme PHP files, particularly around file inclusion: grep -rn "\$_GET\|\$_POST\|\$_REQUEST" wp-content/themes/laurent/ | grep -i "file\|path\|page\|template"
    Affected if Theme files accept file/path parameters from user input and pass them to include/require functions without validation
  5. Test for path traversal capability
    If file inclusion parameters are found, attempt a controlled test with a benign path traversal (e.g., ?file=../../../../wp-config.php or similar) on any theme endpoints that process file parameters - only on non-production systems
    Affected if The theme processes file path parameters and allows traversing outside the intended directory (e.g., responds to ../../../etc/passwd style requests)

A user is affected if the Laurent theme is installed and its code contains include/require statements that use unsanitized user input to control which files are loaded, allowing path 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.

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

Update the Laurent theme to a patched version if available. If no patch exists, implement strict input validation and whitelist-based filtering on all file inclusion functions to prevent path traversal, or disable potentially dangerous include/require functionality.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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