AIL Framework EUVD-2026-87096

Requires an authenticated user-role AIL API client (PR:L) capable of importing crawler captures; the attacker injects JavaScript into the item ID, URL, or screenshot-path fields of a capture, which AIL stores and later renders unescaped in the showDomain.html inline onclick attribute and inline script block. Exploitation is LIMITED by: (1) needing valid API user-role credentials - not unauthenticated; (2) requiring a victim to subsequently open the affected domain page (UI:P), though no interaction beyond viewing is needed once loaded; (3) impact confined to the victim's browser session, with no direct compromise of the AIL server itself. Highest value when the viewing victim is a privileged/admin user.

This is a stored XSS (CWE-79) in AIL Framework's crawler splash domain page. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N, 6.3 Medium) is internally consistent with the description: the attacker must be an authenticated user-role API client (PR:L) who injects payloads via a malicious crawler-capture import, and a victim must load the affected domain view (UI:P/Passive). No impact accrues to the AIL server itself (VC/VI/VA:N); the damage lands in the victim's browser (subsequent-system SC/SI), which is why the vendor sets SC:H/SI:H - though for a typical reflected-in-browser XSS I would rate those as SC:L/SI:L, so 6.3 is arguably slightly high. There is no EPSS score, no CISA KEV listing, and no public exploit code, so this is 'no public exploit identified at time of analysis.' No SSVC data was provided. The realistic risk is moderate-and-targeted rather than broad: exploitation is gated on holding a valid API user role and on a privileged user subsequently viewing the poisoned domain page - but that second condition is plausible because analysts routinely review imported crawler captures, and a successful hit against an admin session enables session hijacking / actions-as-victim. Signals are not conflicting; they consistently point to a genuine-but-bounded, privilege-and-interaction-dependent web bug rather than a mass-exploitable network flaw.

An attacker holding a user-role AIL API client submits a crafted crawler capture whose item ID, URL, or screenshot path fields contain a JavaScript payload, which is stored in the data layer. Later, when any operator - including a privileged admin - opens the affected domain's showDomain page, the payload executes in their browser via the unescaped inline onclick attribute and inline script variable, enabling session hijacking or unauthorized actions as that user. No public exploit code is identified, but the injection point and payload placement are fully documented in the vendor patch diff.