HTML/JavaScript Injection via Incorrect Content-Type in BLU-IC2 and BLU-IC4 APIs
CVE-2025-11925 affects BLU-IC2 and BLU-IC4 through version 1.19.5. One of the affected APIs returns an incorrect HTTP Content-Type header of text/html instead of the expected application/json. According to the provided description, this behavior may allow HTML or JavaScript to be injected into the API reply. In practice, mislabeling a JSON response as HTML can cause clients or browsers to interpret response content in an unsafe context, increasing the risk that injected markup or script is rendered or executed rather than treated as inert data. The issue is described as remotely exploitable and is mapped in the source material to CWE-754.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
text/html content type, the injected content could be rendered or executed in the context of the consuming application or user session. This can lead to client-side code execution, content spoofing, session compromise, unauthorized actions in the victim's browser context, and potential downstream impacts to confidentiality and integrity. The provided source also characterizes the vulnerability as remotely exploitable.Mitigation
If you can’t patch tonight, do this now.
application/json for JSON endpoints. Avoid rendering raw API responses in browser contexts, and apply output encoding and strict client-side handling so response data is treated as data rather than active HTML. Additional browser-side hardening such as a restrictive Content Security Policy may reduce script-execution risk, but it does not replace correcting the server-side content type.Remediation
Patch, then assume compromise.
Content-Type: application/json header rather than text/html. Review all API endpoints for similar response-header mismatches and ensure response bodies are emitted with content types matching their actual format.Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.