CVE-2026-50869
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 · uneditedAn issue in the api/plugin.php component of Bludit v3.19.0 allows attackers to execute a directory traversal via supplying a crafted request.
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 directory traversal vulnerability exists in the api/plugin.php component of Bludit v3.19.0. Attackers can craft malicious requests to access files outside the web root directory, potentially exposing sensitive system files, configuration files, or other application data. The critical CVSS score of 9.8 reflects the ease of exploitation and significant impact on confidentiality and potentially system integrity.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 Bludit installationLocate Bludit by searching for characteristic files such as 'bl-content' directory, 'bl-system' directory, or 'index.php' with Bludit branding in the web root.Affected if Bludit CMS is present on the server
-
Identify Bludit versionCheck the installed Bludit version by examining the version file or constant within the Bludit installation directory, then compare it to the affected version v3.19.0.Affected if The installed version is exactly v3.19.0 or falls within the version range containing v3.19.0
-
Verify api/plugin.php existsCheck if the file 'api/plugin.php' exists within the Bludit web directory structure.Affected if The file api/plugin.php is present and accessible via the web server
-
Confirm API endpoint is enabledInspect Bludit configuration settings to determine whether the API functionality is enabled, or attempt a benign request to the api/plugin.php endpoint to verify it responds.Affected if The API endpoint is accessible and responds to requests
You are affected if Bludit v3.19.0 is installed, the api/plugin.php file exists, and the API endpoint is enabled, allowing directory traversal attacks to access files outside the web root.
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 dataUpdate Bludit to the latest version if a patched release is available. If no patch exists, implement strict input validation on the api/plugin.php file to sanitize file path parameters, and consider disabling the API endpoint if not required.
- 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-50869 — 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-50869 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