CVE-2025-10280
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIdentityIQ 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIdentityIQ web services that return non-HTML content (e.g., JSON, XML) can be accessed via URL paths that cause the Content-Type header to be set to text/html. This causes browsers to interpret the response as HTML, and if the content isn't properly escaped, malicious scripts can execute via reflected XSS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.3= 8.3= 8.4= 8.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IdentityIQ versionLocate the IdentityIQ version by checking the identityiq.properties file (typically in /opt/identityiq/config/ or the deployment directory) or the about page in the IdentityIQ console. Look for the 'buildNumber' or 'version' property.Affected if The installed version is < 8.3, or exactly 8.3, 8.4, or 8.5
-
Identify accessible web service endpointsReview your IdentityIQ deployment for exposed REST API endpoints. Common paths include /identityiq/rest/, /identityiq/service/, or custom endpoints returning JSON or XML responses. Check web server configuration files for mapped URL patterns.Affected if Web service endpoints returning JSON or XML are accessible without authentication or with valid user authentication
-
Test Content-Type header behaviorSend a request to a known web service endpoint (e.g., /identityiq/rest/{endpoint} returning JSON) using different URL path variations or extensions. Inspect the response headers using curl -I or browser developer tools to check if Content-Type is set to text/html instead of application/json or application/xml.Affected if The Content-Type header is set to text/html when the response contains JSON or XML data
-
Verify response content for unescaped scriptExamine the raw response body from the web service endpoint. Check if the JSON/XML payload contains characters like <, >, &, or quotes that could be interpreted as HTML/JavaScript if the response is rendered as HTML. Use curl -v to capture full response details.Affected if The response body contains raw JSON/XML data with unescaped HTML special characters that could execute in an HTML context
You are affected if IdentityIQ version is < 8.3, 8.3, 8.4, or 8.5 AND web service endpoints are accessible AND requests to these endpoints result in text/html Content-Type headers with unescaped content that could be interpreted as script.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.3
Ensure all web service endpoints correctly set Content-Type headers matching the response format and apply proper output encoding/escaping to prevent XSS; consider upgrading to patched versions (8.4p4 or later) when available.
IdentityIQ 8.4p4 (for 8.4 users), IdentityIQ 8.3p5 (for 8.3 users), or latest stable release beyond 8.5
- 1. Identify the current IdentityIQ version by checking the build number in the IdentityIQ administration console or system properties.
- 2. For IdentityIQ 8.3 and earlier: Upgrade to IdentityIQ 8.3p5 or later as this patch level addresses the vulnerability.
- 3. For IdentityIQ 8.4: Upgrade to IdentityIQ 8.4p4 or later as this patch level addresses the vulnerability.
- 4. For IdentityIQ 8.5: Upgrade to the latest available IdentityIQ release (verify with SailPoint that 8.5pX or a newer version contains the fix).
- 5. After upgrading, verify the fix by testing the affected web service endpoints to confirm proper Content-Type headers are returned and no XSS payloads execute.
- 6. Review SailPoint documentation for any post-upgrade configuration steps required.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10280 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data