CVE-2026-24608
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Elated-Themes Laurent Core laurent-core allows PHP Local File Inclusion.This issue affects Laurent Core: from n/a through <= 2.4.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 confidenceLocal File Inclusion (LFI) vulnerability in the Laurent Core WordPress theme allows remote attackers to include arbitrary PHP files from the server due to improper input validation on file inclusion functions. This can lead to sensitive file disclosure and potentially remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Laurent Core theme is installedCheck your WordPress themes directory (wp-content/themes/ or wp-content/themes/laurent-core/) for the Laurent Core theme files. Look for style.css which contains the theme version in the header comment.Affected if The Laurent Core theme files exist in your WordPress installation
-
Identify the installed Laurent Core versionOpen wp-content/themes/laurent-core/style.css and locate the 'Version:' field in the theme header comment. Compare this version number to the patched version if known.Affected if The version cannot be determined or is older than the patched version
-
Locate file inclusion functions in theme codeSearch theme PHP files (particularly in functions.php, includes/, or similar directories) for include, require, include_once, or require_once statements that use dynamic variables (e.g., $_GET, $_POST) without proper sanitization.Affected if File inclusion functions accept user-supplied input without validation
-
Check for vulnerable parameters in the applicationReview the theme code for parameters that accept file paths (e.g., ?file=, ?template=, ?page=) and trace whether these are used in include/require statements.Affected if URL parameters accept file paths that could be manipulated for directory traversal
-
Inspect web server access logs for exploitation attemptsSearch access logs (Apache/nginx) for requests containing directory traversal patterns such as ../, ..\, or absolute paths like /etc/passwd in query parameters linked to the theme.Affected if Recent or historical requests contain traversal patterns targeting the theme
-
Check for unauthorized file access or modificationReview recently modified PHP files in the theme directory and check system files (e.g., /etc/passwd, wp-config.php) for unauthorized access timestamps.Affected if Sensitive files have been accessed or theme files have been modified unexpectedly
You are affected if the Laurent Core theme is installed and the installed version is older than the patched version, or if file inclusion functions accept unsanitized user input.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Laurent Core to the latest patched version. If no patch is available, implement web application firewall rules to block directory traversal patterns (.. /) and restrict file inclusion to whitelisted paths.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24608 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24608 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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