CVE-2026-32364
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 redqteam Turbo Manager turbo-manager allows PHP Local File Inclusion.This issue affects Turbo Manager: from n/a through < 4.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 · high confidenceA Local File Inclusion (LFI) vulnerability exists in redqteam Turbo Manager where user-supplied input is used in PHP include/require statements without proper validation. This allows attackers to read sensitive files on the server filesystem by manipulating file paths, potentially exposing configuration files, credentials, or source code.
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 Turbo Manager installationLocate Turbo Manager files on the server by searching for 'turbo' or 'turbomanager' directories, or check web server document roots for this application.Affected if Turbo Manager is found installed on the server.
-
Determine installed versionCheck version.php, composer.json, or the admin dashboard for the Turbo Manager version number. Compare it to the fixed version 4.0.8.Affected if The installed version is lower than 4.0.8 or the version cannot be determined.
-
Examine PHP include/require usageSearch PHP source files for include, include_once, require, or require_once statements where variables from $_GET, $_POST, or $_REQUEST are used directly in the path argument without sanitization.Affected if User-controlled input (request parameters) flows into include/require statements without validation.
-
Check for file path parametersReview application routes and parameters that accept file or path values, such as 'file', 'path', 'page', 'template', or 'controller' parameters in URL requests.Affected if The application accepts file path parameters that could be manipulated to traverse directories.
-
Test LFI payload capabilityUsing a safe read-only file such as /etc/passwd (if the application is reachable), attempt to include it via suspected vulnerable parameters to confirm the LFI exists.Affected if The application returns contents of arbitrary files from the server filesystem.
A system is affected if redqteam Turbo Manager is installed with a version lower than 4.0.8 and the application accepts unsanitized file path parameters in include/require statements.
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 to Turbo Manager version 4.0.8 or later. Until then, implement strict input validation using allowlists for any file path parameters and ensure include/require statements do not accept user-controlled paths.
4.0.8
- Upgrade redqteam Turbo Manager to version 4.0.8 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32364 — 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-32364 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