CVE-2026-22402
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 pavothemes Triply triply allows PHP Local File Inclusion.This issue affects Triply: from n/a through <= 2.4.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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Triply WordPress theme from pavothemes. The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing attackers to manipulate file paths to include arbitrary local PHP files. This can lead to sensitive data exposure or remote 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Triply theme is installedCheck your WordPress installation for the Triply theme from pavothemes in wp-content/themes/ directory, or via WordPress admin dashboard under Appearance > ThemesAffected if The Triply theme by pavothemes is actively installed on the WordPress site
-
Locate file inclusion functions in theme filesSearch theme PHP files for include, require, include_once, or require_once statements that use variables in the file path without proper validation - examine parameters that could accept user inputAffected if The theme contains include/require statements using unsanitized variables for file paths
-
Identify the vulnerable parameterExamine the file inclusion code to determine which HTTP parameter (GET/POST) controls the file path being includedAffected if A parameter exists that accepts file paths without validation and is used in include/require statements
-
Test for path traversal capabilityIf the vulnerable parameter is identified, attempt to include a known local file using ../ path sequences (e.g., ../../wp-config.php) to confirm path traversal is possibleAffected if The parameter allows directory traversal sequences and successfully includes files outside the intended directory
-
Check if the vulnerable endpoint is accessibleDetermine if the file inclusion functionality is accessible to unauthenticated users or requires authentication, by checking the code for capability checks or nonce validationAffected if The vulnerable file inclusion can be triggered without authentication or proper authorization checks
Your environment is affected if the Triply theme from pavothemes is installed and contains file inclusion code that uses user-controlled parameters without proper validation, allowing path traversal attacks.
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 proper input validation and sanitization on all file inclusion parameters to prevent path traversal attacks. Update to a patched version of the Triply theme when available, or disable the vulnerable file inclusion functionality until a fix can be applied.
- 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-2026-22402 — 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-22402 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