CVE-2026-22425
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 Sweet Jane sweetjane allows PHP Local File Inclusion.This issue affects Sweet Jane: from n/a through <= 1.2.
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 Local File Inclusion (LFI) vulnerability in the Sweet Jane WordPress theme (versions <= 1.2) allows attackers to manipulate PHP include/require statements through unsanitized user input, potentially enabling arbitrary code execution by including malicious local PHP files.
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.
-
Identify if Sweet Jane theme is installedCheck the wp-content/themes/ directory for the sweet-jane or sweet-jane folder, or list all installed themes via WordPress admin under Appearance > ThemesAffected if The Sweet Jane theme folder exists in the WordPress themes directory
-
Determine the installed theme versionOpen the style.css file in the theme folder and look for the 'Version:' comment in the file header, or check theme.json if presentAffected if The version listed is 1.2 or lower (e.g., 1.2, 1.1, 1.0)
-
Locate PHP files using include or require with user inputSearch theme PHP files for patterns like include($_GET, require($_POST, or include_once($_REQUEST using grep or a text editor search within the theme folderAffected if Any PHP file contains dynamic include/require statements using unsanitized superglobal input ($_GET, $_POST, $_REQUEST, etc.)
-
Verify the vulnerable include pattern is reachableExamine the context of the include/require statements found - check if the parameter is used directly without sanitization functions like basename(), realpath(), or allowlist validationAffected if The include/require uses raw user input without path sanitization and is accessible without authentication
If the Sweet Jane theme version is 1.2 or lower AND contains PHP include/require statements using unsanitized user-supplied input, 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 for file paths, avoid using user-supplied input directly in include/require statements, and ensure the application uses a whitelist-based approach for file inclusion.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22425 — 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-22425 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