CVE-2026-25099
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 · uneditedBludit’s API plugin allows an authenticated attacker with a valid API token to upload files of any type and extension without restriction, which can then be executed, leading to Remote Code Execution. This issue was fixed in 3.18.4.
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 confidenceBludit's API plugin allows authenticated users with a valid API token to upload files of any type and extension without proper validation. The unrestricted file upload permits executable files (such as PHP scripts) to be uploaded and subsequently executed, leading to Remote Code Execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.18.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 Bludit installation versionLocate the Bludit installation directory and check the version file (typically VERSION or about.php) or check the admin dashboard for the installed version numberAffected if The installed version is lower than 3.18.4 (e.g., 3.18.3, 3.18.0, 3.15.0, etc.)
-
Verify API plugin is enabledNavigate to the Bludit admin panel, go to Plugins > Installed, and look for the 'API' plugin status; alternatively, check the /bl-content/plugins/ directory for an api folderAffected if The API plugin is installed and enabled on the system
-
Confirm API token configuration existsAccess the API plugin settings in the admin panel under Plugins > API, or check the plugin configuration file in /bl-content/plugins/api/ for defined tokensAffected if One or more API tokens are defined and active for the API plugin
-
Inspect upload directories for unauthorized filesCheck directories where uploaded files are stored (typically /bl-content/uploads/ or custom upload paths configured in the API plugin) for unexpected file extensions such as .php, .phtml, .js, .sh, .exe, or other executable/script typesAffected if Any PHP, Perl, or other script files are present in upload directories that were not intentionally placed there by administrators
A system is affected if it runs Bludit version lower than 3.18.4, has the API plugin enabled with a configured token, and an attacker with that token could upload and execute arbitrary files.
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 · scoped3.18.4
Upgrade to Bludit 3.18.4 or later to apply the vendor patch. Until upgrade is possible, restrict API access to trusted users only and implement server-side allowlist-based file type and extension validation.
3.18.4
- Backup the existing Bludit installation including all files and the database
- Download Bludit version 3.18.4 from the official repository or source
- Replace the existing Bludit files with the new version 3.18.4
- Restore any custom configurations or content from the backup if needed
- Verify the API plugin is updated to the fixed version
- Test that file upload restrictions are now properly enforced
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-25099 — 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-25099 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