CVE-2026-22344
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 Mikado-Themes FiveStar fivestar allows PHP Local File Inclusion.This issue affects FiveStar: from n/a through <= 1.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 confidenceA PHP Local File Inclusion vulnerability exists in the FiveStar theme where user-supplied input is not properly validated before being used in PHP include/require statements. This allows attackers to include arbitrary local PHP files, potentially leading to remote code execution if they can upload malicious files or access sensitive system 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 FiveStar theme is installedSearch for theme files: look for directories named 'fivestar', 'FiveStar', or 'fivestar-theme' in web root themes folder (commonly /wp-content/themes/ for WordPress or similar paths for other CMS). Check theme's style.css or theme.json for theme name metadata.Affected if The FiveStar theme directory exists on the server.
-
Determine FiveStar theme versionLocate the theme's version file, style.css header, or theme.json where version is typically defined. Compare the found version against any release notes or changelogs for the theme.Affected if The installed version is older than the patched version (check vendor advisories for exact version numbers).
-
Identify file inclusion endpointsSearch theme source code for PHP include, require, include_once, or require_once statements that use variables in the path (e.g., include($_GET['page']). Look for parameters that accept file paths in HTTP requests.Affected if The code contains file inclusion using unsanitized user input without proper path validation.
-
Check for accessible upload directoriesReview web server configuration and theme settings to identify upload directories (commonly /uploads/, /files/, /attachments/). Verify if PHP files can be uploaded and are executable from these directories.Affected if PHP execution is enabled in upload directories, allowing uploaded malicious PHP files to be executed.
-
Test for directory traversal vulnerabilityIf file inclusion parameters are found, attempt safe reconnaissance: review server logs for any anomalous include/require requests with '../' sequences, or use a web application scanner to test for LFI. Do not perform active exploitation.Affected if The application allows directory traversal sequences (../) in file inclusion parameters without proper sanitization.
You are affected if the FiveStar theme is installed, contains file inclusion code using unsanitized user input, and the upload directories allow PHP execution, enabling remote code execution via uploaded malicious files.
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 allowlisting for file inclusion paths; upgrade to a patched version when available; disable PHP execution in upload directories; consider deploying a WAF rule to detect and block directory traversal attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22344 — 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-22344 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