Loading vulnerability…
CVE-2026-29519 is a reflected cross-site scripting vulnerability in Lucee CFML Server affecting multiple release lines, including 5.3.x, 6.1.x, 6.2.x, and 7.0.x. The flaw is caused by improper output encoding during URL path parsing, where attacker-controlled content embedded in the request path is reflected in the server response. An unauthenticated remote attacker can craft a malicious link containing HTML or JavaScript payloads in the path so that, when a victim requests the URL, arbitrary script executes in the victim's browser within the application context. The issue is particularly relevant where victims have access to Lucee administrative functionality.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a minimal proof-of-concept for CVE-2026-29519, a reflected XSS vulnerability in Lucee CFML Server URL path parsing. The repository contains only three files: LICENSE, a detailed README.md, and poc.txt. There is no standalone exploit program or automation framework; the actionable exploit content is a single crafted HTTP request that places an HTML tag with JavaScript in the URL path. The exploit capability is browser-side script execution in the context of a vulnerable Lucee-hosted application when a victim visits the malicious URL. The README documents affected versions extensively, provides a Docker-based lab setup using the lucee/lucee:6.2.0.321 image, and shows the vulnerable path pattern /test/<img ... >/index.cfm/. The poc.txt file contains the simplest usable exploit form via curl. Because the payload is only a demonstrative alert() and there is no post-exploitation automation, credential harvesting logic, or reusable tooling, this is best classified as a POC rather than an operational or weaponized exploit. The attack vector is web/network with required user interaction, and the main fingerprintable target pattern is an exposed Lucee endpoint serving CFML content where unsanitized path components are reflected into the response.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.