HendonWordPress extension · Qodeinteractive
CVE-2025-67937
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 Mikado-Themes Hendon hendon allows PHP Local File Inclusion.This issue affects Hendon: from n/a through < 1.7.
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 confidenceThe Hendon WordPress theme by Mikado-Themes contains a Local File Inclusion (LFI) vulnerability where improper control of filenames in PHP include/require statements allows attackers to include arbitrary local PHP files. This is a code-level vulnerability in the theme's PHP files where user-controlled input is not properly sanitized before being used in file inclusion operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
HendonWordPress extension
< 1.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hendon theme versionLocate the theme's style.css file in wp-content/themes/hendon/ and check the 'Version:' header in the CSS comment block at the top of the file. Alternatively, check version defined in the theme's functions.php or version.php file.Affected if The version number displayed is lower than 1.7 (for example, 1.6, 1.5, 1.0, etc.)
-
Review PHP files for include/require statements using variable inputSearch all PHP files within the wp-content/themes/hendon/ directory for include, include_once, require, or require_once statements that use variables or request parameters in the file path (for example: include($file), include($_GET['file']), include($path . $_POST['name']))Affected if Any PHP files contain include/require statements where user-controlled input (GET, POST, REQUEST, or unspecified variables) flows directly into the file path without sanitization or validation checks
-
Check for path traversal patterns in file inclusion codeExamine identified vulnerable include/require statements for lack of basename(), realpath(), or whitelist validation. Look for patterns like 'include($requested_file)' or 'require($folder . $_REQUEST["file"])' without path normalization.Affected if The include/require statements allow direct use of variables without basename(), realpath(), or whitelist filtering, enabling path traversal (for example, ../../wp-config.php)
-
Verify if vulnerable endpoint is accessibleIf the theme has any AJAX handlers, template files, or callback functions that accept file parameters, test whether HTTP requests can trigger the include/require with arbitrary local file paths.Affected if HTTP endpoints exist that accept file path parameters and pass them to include/require without validation
You are affected if the installed Hendon theme version is below 1.7 AND your theme contains PHP include/require statements that use unsanitized user input in the file path, allowing arbitrary local file inclusion.
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.
dbcve · scoped1.7
Upgrade the Hendon theme to version 1.7 or later to obtain the patched version. If immediate upgrade is not possible, audit and harden all include/require statements in the theme to implement strict input validation and path traversal protections.
1.7
- Log in to the WordPress admin dashboard
- Navigate to Appearance > Themes
- If a new version (1.7) is available through the WordPress theme repository or Mikado-Themes, click Update
- If automatic updates are not available, download version 1.7 from the official vendor source
- Backup the current theme files and database before updating
- Deactivate the current Hendon theme, then upload and activate version 1.7
- Verify the theme functions correctly after activation
- Check that the LFI vulnerability is resolved by confirming the include/require statements now properly validate or sanitize file paths
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Hendon
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67937 — 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-2025-67937 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