CVE-2026-32505
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 CreativeWS Kiddy kiddy allows PHP Local File Inclusion.This issue affects Kiddy: from n/a through <= 2.0.8.
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 confidenceLocal File Inclusion vulnerability in CreativeWS Kiddy (version <= 2.0.8) where improper control of filenames in PHP include/require statements allows attackers to manipulate file paths and read sensitive local files from 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.
-
Confirm CreativeWS Kiddy PHP is installedSearch your web root directories for files or directories named 'kiddy', 'CreativeWS', or common PHP entry points from this application. Check your web server configuration for aliases or virtual hosts pointing to this application.Affected if The application is present in your environment
-
Determine the installed versionLocate version information in the application source code - check for VERSION, version.php, or a README/CHANGELOG file within the kiddy application directory. Compare the found version against the affected range (<= 2.0.8).Affected if The installed version is 2.0.8 or lower
-
Identify exposed file inclusion parametersReview PHP source files in the application for include(), require(), include_once(), or require_once() statements that use variables (e.g., include($var) or require($_GET['page'])) without sanitization. Use grep to search for these patterns across PHP files.Affected if User-controllable parameters are used in file inclusion functions without validation
-
Verify PHP configuration allows file inclusion attacksCheck php.ini for the allow_url_include setting. If enabled, remote file inclusion (RFI) becomes possible; combined with LFI, this increases exploitability. Also verify open_basedir restrictions are not in place to limit file system access.Affected if allow_url_include is On or no open_basedir restrictions exist, increasing attack surface
-
Test if file inclusion parameters are reachable via HTTPAttempt to access common entry points with manipulated parameters (e.g., ?page=../../../../etc/passwd or ?file=../../../config.php). Observe if application returns file contents or error messages revealing path traversal.Affected if The application accepts and processes unsanitized input through URL parameters, enabling local file access
You are affected if the CreativeWS Kiddy PHP application version 2.0.8 or lower is installed and contains file inclusion code that processes unsanitized user input from HTTP parameters.
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 dataSanitize and validate all user-supplied input used in include/require statements, implement allowlist-based validation for file paths, and avoid using user input directly in file inclusion functions.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32505 — 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-32505 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