CVE-2026-71447 Stored Cross-Site Scripting in Chat and Forum Translation Controls in ail-framework
Stored XSS in AIL framework allows attackers to inject JavaScript via crafted message IDs, executing code in analysts' browsers upon interaction.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-71447?
CVE-2026-71447 is a medium-severity cross-site scripting vulnerability in ail-project ail-framework, published on 6 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
AIL Project contains a stored cross-site scripting vulnerability in the translation controls displayed for chat messages and forum posts.
The affected templates inserted message and post identifiers directly into inline JavaScript onclick handlers:
onclick="translateMessageToPreferredLanguage('{{ message['id'] }}', '{{ mess_id_escape }}', this)"
and:
onclick="translatePostToPreferredLanguage('{{ post['id'] }}', '{{ post_id_escape }}', this)"
These values were HTML-template escaped but were not safely encoded for use as JavaScript string literals inside an HTML attribute. A specially crafted identifier containing quotation marks, escape characters, or other JavaScript syntax could therefore terminate the expected string argument and inject arbitrary JavaScript into the event handler.
Because the affected values are associated with indexed chat messages or forum posts, a malicious value may remain stored by AIL and be rendered whenever an analyst accesses the corresponding chat or forum explorer view.
Successful exploitation requires the victim to click the affected Translate to preferred language button. The injected code would then execute in the victim’s browser under the security origin of the AIL instance.
Weakness: CWE-79
Which versions are affected by CVE-2026-71447?
How do I fix CVE-2026-71447?
No fix has been published for CVE-2026-71447 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-71447 being exploited?
There is no known exploitation of CVE-2026-71447 in the wild and no public exploit code.
Sources
Also known as GHSA-6vfp-xx86-86wv.