CVE-2026-39552
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 Code Supply Co. Blueprint allows PHP Local File Inclusion. This issue affects Blueprint: from n/a before 1.1.5.
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 Code Supply Co. Blueprint theme. The vulnerability allows attackers to manipulate filename parameters in include/require statements to read sensitive files from the server. This occurs due to improper input validation on file inclusion functions, enabling path traversal attacks.
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 the installed Blueprint versionCheck the version file, changelog, or admin interface of the Blueprint application to determine the current version numberAffected if The installed version is prior to 1.1.5 (e.g., 1.1.4, 1.1.0, etc.)
-
Locate PHP files using include/require statementsSearch the application source code for PHP include, include_once, require, or require_once statements that accept variable inputAffected if The application uses dynamic file inclusion where user-supplied parameters influence the file path in include/require statements
-
Inspect file inclusion parametersExamine the parameters passed to include/require functions and determine if they can be controlled through HTTP request parameters (GET/POST)Affected if User-controllable input is directly or indirectly used in file inclusion without proper validation
-
Check input validation on file path parametersReview the code that processes file path parameters to verify if path sanitization or whitelist validation is implementedAffected if No input validation, path sanitization, or whitelist checking is performed on file path parameters before they are used in include/require statements
-
Verify PHP configuration settingsCheck the PHP configuration file (php.ini) for allow_url_include and other settings that may affect file inclusion behaviorAffected if The application has unprotected file inclusion that could be exploited via LFI even without additional PHP misconfigurations
The environment is affected if Blueprint version is prior to 1.1.5 AND the application contains PHP include/require statements that use user-supplied input without proper validation on file paths.
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.
dbcve · scopedUpgrade Blueprint to version 1.1.5 or later. If immediate upgrade is not possible, implement input validation and path traversal checks on all file inclusion parameters, and disable allow_url_include in PHP configuration.
1.1.5
- Backup your current Code Supply Co. Blueprint installation and database
- Download Blueprint version 1.1.5 from the official vendor source
- Replace the existing Blueprint files with the new version 1.1.5
- Verify the file inclusion vulnerability is resolved by testing the affected functionality
- Confirm all other features work correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39552 — 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-39552 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