CVE-2025-10280: SailPoint Technologies IdentityIQ · XSS or 'Cross-site Scripting'
Affects SailPoint Technologies IdentityIQSource CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2025
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SailPoint Technologies IdentityIQ | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-10280, organizations should first verify if they are running affected versions of SailPoint IdentityIQ (8.3, 8.4 prior to 8.4p4, or 8.5). Since no official patches were linked at disclosure, immediate steps include: 1) Restrict access to IdentityIQ web services that serve non-HTML content via URL filtering or web application firewall (WAF) rules to block suspicious or malformed requests that attempt to manipulate the Content-Type header. 2) Implement strict Content Security Policy (CSP) headers to limit the execution of inline scripts and reduce the impact of XSS attacks. 3) Review and harden HTTP response headers to ensure Content-Type is correctly set and not overridden by user-controllable input. 4) Conduct thorough input validation and output encoding on all user-supplied data within IdentityIQ customizations or integrations. 5) Monitor logs for unusual URL access patterns or error messages indicative of attempted exploitation. 6) Engage with SailPoint support for any available patches or hotfixes and plan for timely upgrades to patched versions once released. 7) Educate users about phishing and suspicious links to reduce the risk of user interaction exploitation.
Description
IdentityIQ 8.5, IdentityIQ 8.4 and all 8.4 patch levels prior to 8.4p4, IdentityIQ 8.3 and all 8.3 patch levels including 8.3p5, and all prior versions allows some IdentityIQ web services that provide non-HTML content to be accessed via a URL path that will set the Content-Type to HTML allowing a requesting browser to interpret content not properly escaped to prevent Cross-Site Scripting (XSS).