CVE-2026-22521
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 G5Theme Handmade Framework handmade-framework allows PHP Local File Inclusion.This issue affects Handmade Framework: from n/a through <= 3.9.
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 in the G5Theme Handmade Framework (handmade-framework versions through 3.9) allows attackers to include arbitrary local PHP files via improper control of filename parameters in include/require statements. This can lead to sensitive file disclosure, code execution, or server compromise.
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 Handmade Framework installationSearch for files belonging to the G5Theme Handmade Framework. Look for directories or files named 'handmade-framework', 'handmade', or check composer.json for 'g5theme/handmade-framework' or similar package references.Affected if The Handmade Framework is not present in the environment.
-
Determine the installed versionCheck the version file, composer.json, or any version.txt/readme.txt shipped with the framework. Look for a version number such as 3.9, 3.8, 3.7, etc.Affected if The installed version is 3.9 or any earlier version (versions through 3.9 are affected).
-
Locate include/require statements with variable parametersSearch the framework PHP files for include, include_once, require, or require_once statements that use variables or parameters in the file path, for example: include($path . $_GET['file']); or require($_REQUEST['template']);Affected if Such vulnerable include/require patterns exist in the framework code.
-
Verify if user input reaches the include/requireTrace the data flow from HTTP request parameters (GET, POST, REQUEST) to the include/require statements found in the previous step. Check if these parameters are used without sanitization or validation.Affected if User-controllable input can reach the include/require statements without proper validation.
The environment is affected if the installed Handmade Framework version is 3.9 or below and the vulnerable include/require patterns with unsanitized user input exist in the codebase.
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 whitelisting for all include/require parameters, ensuring only predefined allowed files can be included. Alternatively, upgrade to a patched version of the Handmade Framework if available.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22521 — 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-22521 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