Agora Project EUVD-2026-100476

The attacker must hold an authenticated account with access to the LDAP/person import feature of Agora Project and must submit the payload specifically as a two-dimensional (nested) POST array, because the flaw is that paramsFilter() does not recurse into nested arrays - a flat parameter would be sanitized. Exploitation is further limited by requiring a second user to subsequently view the poisoned user profile for the script to execute (passive user interaction), and it affects only deployments running a version before 26.10.0. There is no server-side code execution or data impact; impact is confined to the victim's browser context.

This is a moderate, not a priority-one, issue. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P) and the resulting 5.1 base score are internally consistent with the description: a network-reachable but authenticated (PR:L) stored XSS that requires a victim to passively view (UI:P) a poisoned profile. The vector correctly sets vulnerable-system impact to none (VC:N/VI:N/VA:N) and places the only impact on the subsequent system - the victim's browser session - at SC:L/SI:L, which matches a reflected-into-browser script with no direct server compromise. No KEV listing and no public proof-of-concept were provided, so exploitation status is 'no public exploit identified at time of analysis'; EPSS was not supplied. There are no conflicting signals here - all sources agree this is a credentialed, interaction-dependent XSS against a niche collaboration product. The main caveat is that real-world risk depends on how many low-privileged accounts can reach the LDAP/person import flow, which the data does not quantify.

An authenticated low-privilege user abuses the LDAP/person import flow to submit a malicious value inside a two-dimensional (nested) POST array, which slips past the paramsFilter() sanitizer because that filter does not recurse into nested arrays. The unneutralized markup is stored in a user profile; when another user (including an administrator) later views that profile, the injected script executes in their browser. No public exploit code was identified, and the attack requires the victim to view the affected page.