CVE-2026-12228: Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
A stored cross-site scripting (XSS) vulnerability exists in the `POST /api/prompts/share` endpoint of parisneo/lollms (latest version). The endpoint stores attacker-controlled `prompt_content` into `DBDirectMessage.content` without server-side sanitization. When a victim opens the direct message (DM) thread, the message is rendered by the DM UI through `MessageContentRenderer`, which uses `v-html` to insert rendered HTML into the DOM. The frontend sanitizer, which is regex-based, fails to comprehensively sanitize attacker-controlled HTML, allowing malicious payloads to execute in the victim’s browser context. This vulnerability enables any authenticated user to send a malicious prompt-share message to another user’s inbox, leading to arbitrary JavaScript execution, authenticated actions as the victim, exposure of same-origin application data, and potential account takeover.
Description quoted from the CVE record (assigned by @huntr_ai, published 2026-07-18).
Weakness: CWE-79 Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)
How it can be exploited
Exploitable over the network with low attack complexity needing low privileges and a user must take an action. Impact: confidentiality high, integrity high, availability none. CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-45401, GHSA-vh8r-6pw6-wv4f
VEDAS cluster: VEDAS:FOXTROTFIST
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-12228.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-12228.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-12228.rules
Vulnerability databases and vendor advisories (4)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-45401
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-vh8r-6pw6-wv4f
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-12228
- Vulnerability database or vendor advisory: https://osv.dev/vulnerability/CVE-2026-12228
1 more reference returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.972
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| parisneo parisneo/lollms | up to and including latest | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: lollms lollms.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-12228 lollms - Stored XSS via prompts share prompt_content. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-12228 lollms - Stored XSS via prompts share prompt_content"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/prompts/share"; nocase; fast_pattern; http.request_body; content:"prompt_content"; nocase; pcre:"/prompt_content\x22\s*:\s*\x22(?:[^\x22]|\\\x22)*(?:<script|<svg|<img|<iframe|onerror\s*=|onload\s*=|javascript:)/i"; classtype:web-application-attack; reference:cve,CVE-2026-12228; reference:url,https://www.exploit.observer/?keyword=CVE-2026-12228&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=lollms&match=exact; sid:1099806; rev:1;)
CVE-2026-12228.rules on GitHub
References
Other references
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.