Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-25099: Bludit API Plugin Unrestricted File Upload RCE

Published Mar 27, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS2.0%81st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Bludit
IdentifiersCVE-2026-25099CWE-434 · Unrestricted Upload of File with…

CVE-2026-25099 is an unrestricted file upload vulnerability in Bludit’s API plugin affecting Bludit versions before 3.18.4. The API plugin permits an authenticated attacker possessing a valid API token to upload files of any type and extension without adequate restriction or validation. Because the uploaded file can subsequently be executed by the application environment, the flaw can be leveraged for remote code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in remote code execution in the context of the affected Bludit application. An attacker can upload a server-executable payload and execute arbitrary code, which may enable full compromise of the CMS instance, unauthorized access to data, modification of site content, deployment of additional malware or web shells, and disruption of service availability.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable or restrict the Bludit API plugin, revoke and rotate exposed or unnecessary API tokens, and limit API access to trusted administrative networks or hosts. Additionally, configure the web server and upload directories so uploaded files cannot be executed, and monitor for suspicious file uploads or unexpected executable content in web-accessible paths.

Remediation

Patch, then assume compromise.

Upgrade Bludit to version 3.18.4 or later, which fixes this issue. Ensure the API plugin enforces strict server-side validation of uploaded files, including allowlisting of safe file types and extensions and preventing execution of uploaded content.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-25099This repository is a small standalone Python proof-of-concept exploit for CVE-2026-25099 affecting Bludit CMS versions earlier than 3.18.4. It contains two files: the main exploit script, CVE-2026-25099.py, and a README describing usage, affected versions, remediation, and sample output. The exploit automates a full authenticated attack chain against Bludit's API plugin. First, it queries GET /api/pages with a provided API token to obtain a valid page key. Next, it abuses POST /api/files/<page-key> to upload an arbitrary PHP file because the vulnerable endpoint does not validate file extension or content. The script generates a random .php filename and uploads a minimal webshell that executes commands passed through the cmd request parameter using PHP's system() function. After upload, it derives the expected public shell location under /bl-content/uploads/pages/<page-key>/<random>.php, verifies code execution by running id, and then either executes a single operator-supplied command or enters an interactive command loop. Structurally, the Python code is straightforward and organized into helper functions: get_page_key() for API enumeration, upload_shell() for exploitation, execute_command() for post-exploitation command execution, and main() for CLI handling and workflow orchestration. It uses argparse for command-line arguments and requests for HTTP communication. There is no framework dependency, no persistence logic, and no advanced evasion or payload staging. The exploit is operational because it includes a working payload and interactive command execution, but it is still a simple PoC-style tool rather than a heavily weaponized framework module. The main capability is authenticated remote code execution via arbitrary file upload leading to a webshell. The key prerequisite is possession of a valid Bludit API token and access to a vulnerable instance with the API plugin enabled.yahiahamza · Disclosed Mar 28, 2026 · python · markdown · web · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BluditBluditapplication
FAQ

Frequently asked questions

Is CVE-2026-25099 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-25099 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-25099?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-25099, the earliest disclosed Mar 28, 2026.
Is there a patch for CVE-2026-25099?
Upgrade Bludit to version 3.18.4 or later, which fixes this issue. Ensure the API plugin enforces strict server-side validation of uploaded files, including allowlisting of safe file types and extensions and preventing execution of uploaded content.
What products are affected by CVE-2026-25099?
Bludit.
How severe is CVE-2026-25099?
CVE-2026-25099 has a CVSS v4 score of 8.7 (High) and an EPSS score of 2.0% (81st percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.