dbcve.org
Identity ServerApplication · Wso2

CVE-2025-0209

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A reflected cross-site scripting (XSS) vulnerability exists in the account registration flow of WSO2 Identity Server due to improper output encoding. A malicious actor can exploit this vulnerability by injecting a crafted payload that is reflected in the server response, enabling the execution of arbitrary JavaScript in the victim's browser. This vulnerability could allow attackers to redirect users to malicious websites, modify the user interface, or exfiltrate data from the browser. However, session-related sensitive cookies are protected using the httpOnly flag, which mitigates the risk of session hijacking.

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 · high confidence

This is a reflected cross-site scripting (XSS) vulnerability in the account registration flow of WSO2 Identity Server. The vulnerability stems from improper output encoding, allowing attackers to inject malicious JavaScript payloads that get reflected in the server response and executed in victims' browsers.

MitigationApply proper output encoding (HTML entity encoding) to all user-supplied input in the registration flow before rendering it in responses. Validate and sanitize all inputs according to OWASP XSS prevention guidelines.

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
Identity ServerApplication
Affected:= 7.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify WSO2 Identity Server version
    Check the product version by inspecting the <IS_HOME>/bin/wso2server.bat or wso2server.sh banner, or the product.xml file in <IS_HOME>/repository/components/p2/org.eclipse.equinox.p2.engine/, or by accessing the /carbon/admin/login.jsp page which displays the version
    Affected if The installed version is exactly 7.0.0
  2. Verify account registration is enabled
    Check if the self-registration feature is enabled in <IS_HOME>/repository/conf/deployment.toml under the [identity_mgt.password_reset] or [identity_mgt.user_self_registration] section, or via the WSO2 Admin Console under Identity Providers > Resident > User Onboarding > Self Registration
    Affected if Self-registration is enabled (self_registration.enable = true)
  3. Inspect registration endpoint response handling
    Examine the account-registration endpoint response for proper output encoding. Access the /accountrecoveryendpoint/register.do endpoint and submit a test registration with a special character (e.g., <script>alert(1)</script>) in a field like firstName or lastName, then inspect the HTML source of the response page to see if the input is HTML-encoded or reflected raw
    Affected if User-supplied input appears unencoded/raw in the HTTP response (e.g., <script> tags not converted to &lt;script&gt;)
  4. Review identity-provider-mgt configuration
    Check <IS_HOME>/repository/conf/deployment.toml for the [identity_provider] section and verify how user claims are mapped in the outbound provisioning configuration. Also review <IS_HOME>/repository/components/apps/identity/content/account-recovery/ to see if JSP files perform proper HTML encoding before rendering user input
    Affected if Claims are passed to views without HTML entity encoding, or custom JSPs in the registration flow do not use ESAPI or equivalent encoding functions

You are affected if WSO2 Identity Server 7.0.0 is running with self-registration enabled AND user input in the registration flow is reflected unencoded in server responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper output encoding (HTML entity encoding) to all user-supplied input in the registration flow before rendering it in responses. Validate and sanitize all inputs according to OWASP XSS prevention guidelines.

Fix this in Identity Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0209 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0209 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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