CVE-2026-22362
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 axiomthemes Photolia photolia allows PHP Local File Inclusion.This issue affects Photolia: from n/a through <= 1.0.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 Local File Inclusion (LFI) vulnerability exists in the Photolia PHP theme where user-controlled input is passed to PHP include/require statements without proper validation, allowing attackers to read sensitive local files on the server.
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 Photolia PHP theme installationSearch for files named 'photolia', 'theme', or directories containing PHP files with theme-related naming conventions. Common locations include /wp-content/themes/, /themes/, or document root directories.Affected if The Photolia PHP theme files are present on the server.
-
Identify Photolia theme versionCheck for a version.php, info.xml, style.css with theme header, or any VERSION constant file within the Photolia theme directory. Compare the found version against any known affected version ranges.Affected if The installed version falls within the affected version range (if known) or cannot be determined.
-
Find PHP include/require statements using user inputSearch the Photolia theme PHP files for patterns like 'include($_GET', 'require($_GET', 'include($_POST', 'require($_REQUEST', or similar where superglobal arrays are passed directly to include/require statements.Affected if Code patterns where $_GET, $_POST, or $_REQUEST parameters are directly used in include/require statements without sanitization are found.
-
Identify vulnerable URL parametersExamine the include/require statements found in step 3 to identify which specific parameters (e.g., ?page=, ?file=, ?theme=) are passed to the include/require function. Test if these parameters accept arbitrary file paths.Affected if User-supplied parameters can be manipulated to include arbitrary local files (e.g., ../../etc/passwd).
A user is affected if the Photolia PHP theme is installed and code exists where user-controlled input from GET/POST/REQUEST parameters is directly used in PHP include or require statements without validation.
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 and use an allowlist approach for file inclusion, avoiding direct use of user input in include/require statements.
- 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-22362 — 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-22362 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