dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-29519

HIGH · 8.2 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges 6 weeks old

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 · unedited
Lucee CFML Server versions across the 5.3.x, 6.1.x, 6.2.x, and 7.0.x release lines contain a reflected cross-site scripting vulnerability in URL path parsing that allows unauthenticated remote attackers to execute arbitrary JavaScript in a victim's browser by embedding HTML or JavaScript payloads within the request path. Attackers can craft a malicious URL containing injected script content that is reflected in the server's response without proper output encoding, enabling session hijacking or unauthorized actions against the Lucee administrative interface when a victim visits the crafted link.

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 confidence

Lucee CFML Server versions 5.3.x through 7.0.x contain a reflected cross-site scripting vulnerability in URL path parsing. Unauthenticated remote attackers can inject HTML or JavaScript payloads into the request path, which is reflected in the server's response without proper output encoding, enabling session hijacking or administrative interface compromise.

MitigationApply any available vendor patch for Lucee CFML Server; until patched, implement web application firewall rules or reverse proxy filtering to sanitize URL path inputs before reaching the Lucee server.

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
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Lucee CFML Server is running
    Check for Lucee by accessing the server's root URL or admin interface (e.g., /lucee/admin or /index.cfm). Lucee typically serves a default welcome page or admin login.
    Affected if The target is not Lucee CFML Server
  2. Identify installed Lucee version
    Access the Lucee Administrator web interface (typically at /lucee/admin/server.cfm) and locate the version number displayed on the server or about page. Alternatively, check server startup logs or the lucee-server.xml configuration file for the version attribute.
    Affected if Version cannot be determined or is not within 5.3.x to 7.0.x inclusive
  3. Verify version falls within affected range
    Compare the identified version against the affected range: 5.3.x through 7.0.x (all minor versions in between are affected). Versions below 5.3.0 or above 7.0.x (if such exist) are not affected.
    Affected if Version is 5.3.0 through 7.0.x inclusive
  4. Test for reflected XSS in URL path
    Send an HTTP request to the server with a non-existent path containing a test XSS payload, such as GET /<script>alert(1)</script> HTTP/1.1, and examine the response body to see if the payload is reflected without HTML encoding (raw <script> tags visible).
    Affected if The payload reflects in the response as raw HTML/JavaScript without encoding

The environment is affected if Lucee CFML Server versions 5.3.x through 7.0.x are running and URL path input is reflected in responses without proper HTML encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available vendor patch for Lucee CFML Server; until patched, implement web application firewall rules or reverse proxy filtering to sanitize URL path inputs before reaching the Lucee server.

Recommended fix Moderate confidence

Lucee 5.4.x (for 5.3.x), Lucee 6.3.x (for 6.1.x/6.2.x), or Lucee 7.1.x (for 7.0.x)

  1. 1. Identify the currently running Lucee version by checking the Lucee Administrator or server configuration
  2. 2. For Lucee 5.3.x users: Upgrade to Lucee 5.4.x (latest 5.x release) which contains the security fix
  3. 3. For Lucee 6.1.x users: Upgrade to Lucee 6.2.x or later (preferably 6.3.x) which contains the security fix
  4. 4. For Lucee 6.2.x users: Upgrade to Lucee 6.3.x (latest 6.x release) which contains the security fix
  5. 5. For Lucee 7.0.x users: Upgrade to Lucee 7.1.x or latest 7.x release which contains the security fix
  6. 6. After upgrade, verify the fix by testing URL path injection scenarios and confirm JavaScript is properly encoded in responses
  7. 7. Clear any cached templates and restart the Lucee service to ensure the new version is fully active
Caveat Upgrading across major version lines (e.g., 5.x to 6.x or 6.x to 7.x) may introduce breaking changes to existing code, custom tags, or extensions; review the release notes for each major version jump

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29519 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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