CVE-2026-24390
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 QantumThemes Kentha Elementor Widgets kentha-elementor allows PHP Local File Inclusion.This issue affects Kentha Elementor Widgets: 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 confidenceLocal File Inclusion vulnerability in QantumThemes Kentha Elementor Widgets allows attackers to include arbitrary local PHP files via improper control of filename parameters in include/require statements. This can lead to disclosure of sensitive files, code execution, or complete system compromise.
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.
-
Identify Kentha Elementor Widgets versionLocate the Kentha Elementor Widgets plugin/theme folder in your WordPress installation (typically in wp-content/themes/kentha or wp-content/plugins/kentha-elementor-widgets) and check the main PHP file for a version constant or header comment (e.g., 'Version: x.x.x')Affected if The installed version is lower than 3.1 or the version cannot be determined
-
Locate the vulnerable file inclusion codeSearch the Kentha Elementor Widgets directory for PHP files containing include(), require(), include_once(), or require_once() statements that use variables in the file path (e.g., include($file), require($_GET['file'])Affected if Such patterns exist and the included files are accessible without authentication
-
Inspect the parameter handling in include statementsExamine the identified include/require files to determine if user-supplied parameters (from $_GET, $_POST, or $_REQUEST) are used directly in file paths without sanitizationAffected if File inclusion parameters are not validated, sanitized, or restricted to allowed paths
-
Check for sensitive file exposureAttempt to access known sensitive files through the suspected LFI parameters (e.g., ../../wp-config.php, /etc/passwd) using a controlled request to confirm if the vulnerability exists in your environmentAffected if The application returns file contents from paths outside the intended directory
-
Verify PHP allow_url_include settingCheck your php.ini or run phpinfo() to determine if the allow_url_include directive is enabled (this affects the severity of LFI if combined with remote file inclusion)Affected if allow_url_include is enabled (note: this increases exploit severity but is not required for basic LFI)
Your environment is affected if Kentha Elementor Widgets version is below 3.1 and the vulnerable include/require code patterns with unsanitized parameters exist in your installation.
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 dataUpgrade Kentha Elementor Widgets to version 3.1 or later. If immediate upgrade is not possible, implement input validation and path sanitization on all user-supplied file inclusion parameters, and disable allow_url_include in PHP configuration.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24390 — 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-24390 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