Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Agora messenger
-
DeliveryCraft message with malicious iframe
-
ExploitBypass HTMLPurifier SafeIframe filter
-
ExecutionMessage stored and auto-rendered to channel members
-
ImpactExecute framed JS / drive-by download in victims' browsers
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated Agora Project account (PR:L) with permission to post messages into a channel; the attacker must share that channel with intended victims. Exploitation flows specifically through the messenger feature's HTMLPurifier SafeIframe handling, which permits attacker-controlled iframe markup. No victim interaction beyond viewing the channel is needed (UI:N) because stored messages are automatically rendered to other members, enabling zero-click execution. Limiting factors: valid authentication is mandatory, exploitation is scoped to users who are members of the same channel, and instances upgraded to 26.10.0 or later are not affected. |
| Impact | This is a medium-severity stored XSS (CVSS 4.0 base 5.3, CWE-79) in the Agora Project messenger, and the real-world priority is moderate rather than urgent. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) shows a network-reachable, low-complexity flaw that requires authentication (PR:L) but no victim interaction (UI:N) because the malicious iframe is auto-rendered to channel members - this zero-click delivery is the main risk amplifier. Impact is deliberately scored low: all vulnerable-system impacts are N and only subsequent-system confidentiality/integrity are Low (SC:L/SI:L), reflecting script execution confined to recipients' browser context rather than server compromise. No EPSS score, no CISA KEV listing, and no POC were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the lack of an EPSS value means exploitation probability cannot be quantified from the input. The dominant limiting factor is the authentication requirement - an attacker needs a valid account and shared channel, making this most relevant as an insider/post-compromise or multi-tenant abuse vector rather than an internet-wide drive-by. Net: a legitimate but not emergency-grade issue; patch during normal cycles. |
| Exploit ScenarioDerived | An authenticated user with access to a channel posts a message containing a crafted iframe that slips through HTMLPurifier's SafeIframe allowance in the messenger. When other channel members simply open the conversation, the iframe renders automatically with no clicks required, triggering a drive-by download or executing attacker-framed JavaScript in each victim's browser session. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Stored cross-site scripting in Omnispace Agora Project before 26.10.0 lets an authenticated user post a message containing attacker-controlled iframe markup that survives the messenger's HTMLPurifier SafeIframe handling; the message is persisted and automatically rendered to every other member of the same channel, producing zero-click framed JavaScript execution and drive-by download delivery inside victims' browsers. Exploitation requires a valid Agora Project account with permission to post into a channel and shared channel membership with the intended victims, which confines the practical blast radius to that channel's participants and keeps priority moderate rather than urgent (CVSS 4.0 base 5.3, CWE-79, scoped impact S:C with low confidentiality and integrity effects). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; the vendor has addressed it in the 26.10.0 release.
RemediationAI
The primary fix is to upgrade Agora Project to 26.10.0 (vendor-released patch: 26.10.0), available from the vendor release page at https://github.com/xech/agora-project/releases/tag/26.10 and referenced from https://www.agora-project.net/ and the VulnCheck advisory https://www.vulncheck.com/advisories/omnispace-agora-project-stored-xss-via-messenger-iframe; this release also adds a two-factor authentication option, so enabling 2FA on accounts with messenger posting rights is a worthwhile follow-on hardening step that raises the cost of the authenticated access the flaw requires. Where immediate upgrade is not possible, the most direct compensating control is to remove or restrict the SafeIframe allowance in the HTMLPurifier configuration so that iframe elements are stripped from stored messages - the trade-off is that legitimate embedded content such as videos or external widgets in messages will no longer render, which is usually acceptable in an internal collaboration workspace. Additionally, tighten who may post into channels that include sensitive users, and audit or purge recent messenger content for unexpected iframe markup, though note that restricting messenger usage degrades collaboration for the same user population the attacker abuses. Because exploitation is scoped to members of a shared channel and requires a valid authenticated account, network-perimeter controls are of limited value here; prioritize patching and, if that is delayed, consider disabling the messenger feature entirely for channels that mix trusted and untrusted users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-79 (improper neutralization of input during web page generation) in the messenger's rich-text pipeline. Agora Project passes user-authored message content through HTMLPurifier, an HTML sanitization library, and the deployment enables the SafeIframe branch, a deliberate configuration that permits iframe elements so legitimate embeds can be posted. That whitelist is not constrained tightly enough on the iframe attributes and origin of embedded content, so attacker-supplied iframe markup is preserved rather than stripped when the message is stored. Because Agora renders stored channel messages to all members without further user action, the sanitized-but-still-malicious markup executes in each recipient's browser context, which is why the CVSS assessment carries Scope:Changed (S:C) - the vulnerable server-side component yields impact in the client browser - with low Confidentiality and Integrity impact and no Availability impact. In CVSS 4.0 terms the same behavior maps to subsequent-system low Confidentiality/Integrity impact. The fix in 26.10.0 targets the iframe handling path in the messenger so that attacker-controlled frame sources no longer persist into rendered message bodies.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Authenticated poster gives PR:L; stored iframe auto-renders so UI:N; execution in victim browser crosses trust boundary giving S:C with low C/I and no availability impact.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
1DescriptionCVE.org
Omnispace Agora Project before 26.10.0 contains a stored cross-site scripting vulnerability that allows authenticated users to post messages containing attacker-controlled iframes through the messenger's HTMLPurifier SafeIframe branch. Attackers can craft a message with a malicious iframe that is stored and automatically rendered to other channel members, enabling zero-click drive-by downloads and framed JavaScript execution in recipients' browsers.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-100478
GHSA-qgfm-25pr-4ww7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB