CVE-2026-22449
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 Select-Themes Don Peppe donpeppe allows PHP Local File Inclusion.This issue affects Don Peppe: from n/a through <= 1.3.
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 the Don Peppe WordPress theme allows attackers to manipulate filename parameters in PHP include/require statements to read sensitive local files or potentially achieve remote code execution through path traversal attacks.
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.
-
Locate Don Peppe theme installationCheck the WordPress themes directory at wp-content/themes/ for a folder named 'don-peppe', 'don-peppe', or similar. List all directories in the themes folder and look for the Don Peppe theme.Affected if The Don Peppe theme folder exists in the WordPress themes directory.
-
Identify theme versionOpen the style.css file inside the Don Peppe theme folder and look for the 'Version:' header in the CSS comment block at the top of the file.Affected if A Version header is found with any version number, indicating the theme is installed.
-
Find PHP files with include/require statementsSearch the Don Peppe theme folder for .php files that contain 'include' or 'require' statements. Use: grep -r 'include\|require' *.php or manually inspect PHP files in the theme folder.Affected if PHP files containing include or require statements are found in the theme.
-
Check for user input in file operationsExamine the PHP files found in step 3. Look for patterns where $_GET, $_POST, $_REQUEST, or other user-supplied data is used directly in include(), require(), include_once(), or require_once() functions without sanitization.Affected if User-supplied input (from $_GET, $_POST, etc.) is used directly in include/require statements without validation or sanitization functions like basename().
If the Don Peppe theme is installed and contains PHP files that use user input in include/require statements without proper validation, the environment is affected by this LFI vulnerability.
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 allowlists, sanitize all user-supplied input with basename(), and avoid using user input directly in include/require statements.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.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-22449 — 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-22449 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