CVE-2024-52951: Omada Identity · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 8.0 High · fixed in 15.1 : patch affected systems soon.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 15.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Organizations should prioritize upgrading Omada Identity to version 15 update 1 or later once available to eliminate the vulnerability. If you cannot patch yet, administrators should restrict access to the Access Request History feature to only trusted users and monitor for unusual activity indicative of exploitation attempts. Implementing strict input validation and output encoding on all user-supplied data in the Access Request History can reduce risk. Additionally, deploying Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Security teams should educate users about the risks of clicking suspicious links and encourage cautious behavior. Regularly auditing logs for anomalous access patterns and employing web application firewalls (WAFs) with rules targeting XSS attacks may provide temporary protection. Finally, organizations should prepare incident response plans specific to XSS exploitation scenarios to minimize damage if an attack occurs.
Description
Stored Cross-Site Scripting in the Access Request History in Omada Identity before version 15 update 1 allows an authenticated attacker to execute arbitrary code in the browser of a victim via a specially crafted link or by viewing a manipulated Access Request History