CVE-2026-22502
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 AncoraThemes Mr. Cobbler mr-cobbler allows PHP Local File Inclusion.This issue affects Mr. Cobbler: from n/a through <= 1.1.9.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the Mr. Cobbler theme by AncoraThemes. The vulnerability allows attackers to manipulate file inclusion paths to read sensitive local files or potentially execute arbitrary PHP code. With a CVSS score of 8.1 (HIGH), this represents a significant security risk.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Mr. Cobbler theme installationLocate the theme files in your WordPress installation under wp-content/themes/ and verify the directory named 'mr-cobbler' or 'mr_cobbler' existsAffected if The theme directory is present in the themes folder
-
Identify the theme versionOpen the theme's style.css file (wp-content/themes/mr-cobbler/style.css) and locate the 'Version:' header in the comment block at the topAffected if The version listed cannot be confirmed as patched or is earlier than any vendor-provided fixed version
-
Inspect file inclusion functionsSearch theme PHP files (particularly functions.php, header.php, footer.php, and any template files) for include, include_once, require, or require_once statements that use variables in the path without proper sanitization (e.g., include($template) or include($_GET['page']))Affected if Unsanitized variable-based file inclusions are found that accept user input
-
Check for vulnerable LFI parametersReview URL parameters used in theme templates - look for parameters like 'file', 'page', 'template', 'path', or 'include' that are passed to file inclusion functions without basename() or realpath() validationAffected if Parameters that control file inclusion paths are accessible via GET/POST and not properly validated
Your environment is affected if the Mr. Cobbler theme by AncoraThemes is installed and contains unsanitized file inclusion logic that allows manipulation of file paths through HTTP parameters.
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 dataImplement strict input validation using whitelisting for allowed files, sanitize file inclusion paths with basename() and realpath() functions, and ensure allow_url_include is disabled in PHP configuration.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22502 — 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-22502 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