CVE-2026-22493
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 Gaspard gaspard allows PHP Local File Inclusion.This issue affects Gaspard: 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 confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the Gaspard WordPress theme due to improper control of filename parameters in include/require statements. This allows authenticated attackers to include arbitrary PHP files from the server file system, potentially leading to code execution.
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 Gaspard theme is installedLocate the theme directory: look for /wp-content/themes/gaspard/ or check via WordPress admin under Appearance > ThemesAffected if The Gaspard theme directory exists in the WordPress themes folder
-
Determine Gaspard theme versionOpen /wp-content/themes/gaspard/style.css and read the 'Version:' header in the theme comments, or check version in functions.phpAffected if Version is unknown, unpatched, or within any vulnerable range
-
Locate vulnerable file inclusion codeSearch theme PHP files for include/require statements using dynamic filename variables, e.g., grep -r 'include.*\$_' or 'require.*\$_(GET|POST|REQUEST)' in the gaspard theme directoryAffected if Code contains include/require statements that use unsanitized user-supplied parameters for file paths
-
Check for path traversal patterns in inclusion codeExamine any dynamic include/require calls for lack of basename(), realpath(), or whitelist validation; look for patterns like include($_GET['file']) without sanitizationAffected if File inclusion allows path traversal (e.g., ../../) or arbitrary file paths without validation
-
Verify authentication vector existsCheck WordPress settings at /wp-admin/options-general.php or test if user registration is enabled; determine if attacker can obtain contributor-level or higher accountAffected if User registration is open OR attacker can obtain valid credentials to any privilege level
If Gaspard theme is installed with a vulnerable version containing unsanitized dynamic file inclusion and an attacker can obtain authenticated access, 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 dataUpdate the Gaspard theme to the latest patched version. If no patch is available, implement strict input validation and whitelist-based filtering on all file inclusion parameters to prevent path traversal attacks.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22493 — 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-22493 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