Eleveo Quality Management CVE-2026-85406

Exploitation requires two conditions: the attacker must hold a low-privileged authenticated session in Eleveo Quality Management 9.7.0, and a separate victim user must passively view the Conversation Review entry containing the injected payload (UI:P in CVSS 4.0). The Conversation Review component must be accessible and in use - deployments that have this feature disabled or restricted to a single non-shared account are not exploitable. What limits exploitation: authentication is required (PR:L); unauthenticated exploitation is not possible per the CVSS vector. The impact is further limited to integrity only (VI:L), with no confidentiality or availability effect confirmed in the CVSS 4.0 assessment, though session theft via XSS remains a secondary risk depending on cookie configuration.

Real-world risk is moderate-to-low despite public POC availability. The CVSS 4.0 base score of 5.1 reflects the constrained impact: no confidentiality compromise (VC:N), only limited integrity impact (VI:L), and no availability effect. The attack requires an authenticated low-privileged session and a second user to passively view the injected content - both conditions that reduce automatable exploitation at scale, meaning even a mid-sized municipal IT team in tczew operating a call-center QA platform should treat this as a measured risk rather than an emergency. EPSS data is not provided, so exploitation probability cannot be quantified independently. No CISA KEV listing exists, and no reports of active in-the-wild exploitation were found in the referenced intelligence. The primary concern is insider-threat or persistent stored-XSS scenarios within the contact center reviewer workflow, potentially enabling session hijacking or privilege escalation within the application if session cookies lack HttpOnly protection.

An authenticated low-privileged agent or quality reviewer injects a JavaScript payload into a conversation record within the Conversation Review interface - for example, embedding a script tag in a comment or annotation field. When a supervisor or senior reviewer subsequently opens the same conversation, the script executes in their browser, potentially exfiltrating their session token to an attacker-controlled endpoint. A public proof-of-concept exploit has been disclosed, making adaptation of this attack straightforward for any authenticated user of the platform.