CVE-2025-12627

Improper Refresh Token Implementation via User Impersonation Flow in WSO2 Identity Server Enables Continued Unauthorized Actions

Published Aug 6, 2026 CVSS 3.1 · 2.4 Low EPSS < 1% KEV · Not listed
Description
The user impersonation flow in WSO2 Identity Server fails to properly manage refresh tokens associated with impersonated sessions. This allows an attacker who has obtained an access token for an impersonated user to leverage the refresh token grant to obtain new access tokens, extending their ability to act as the legitimate user.

An attacker who gains access to an impersonated user's access token can exploit this weakness to renew their authorization. This results in the continued ability to perform actions on behalf of the actual user, compromising log integrity and traceability by masking the true actor.

Analysis

AI-generated

Technical impact

The vulnerability lies in WSO2 Identity Server’s user impersonation flow, which fails to restrict the use of refresh tokens for impersonated sessions. An attacker who has already obtained an access token for an impersonated user can invoke the refresh token grant to receive new access tokens, thereby extending the window of unauthorized actions. While the CVSS score of 2.4 indicates a low overall severity, the flaw compromises log integrity and traceability, masking the true actor behind continued actions.

Affected Systems

The flaw affects all versions of WSO2 Carbon OAuth and WSO2 Identity Server. No specific version information is provided, so all releases should be considered potentially vulnerable until a patch is applied.

Risk and Exploitability

The CVSS score of 2.4 and the absence of EPSS data suggest a low likelihood of widespread exploitation, and the flaw is not listed in CISA’s KEV catalog. However, if an attacker can acquire an impersonated user’s access token, they can repeatedly renew it via the refresh token grant. The attack vector is a legitimate OAuth flow that does not require elevated privileges beyond the impersonated credential, making the vulnerability exploitable in environments where user impersonation is enabled and tokens are not tightly controlled.

Remediation

Vendor Solution

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4619/#solution


OpenCVE Recommended Actions

  • Apply the vendor‑issued patch detailed at the WSO2 security advisory link.
  • Limit the use of the user impersonation flow to trusted administrators and monitor which accounts are allowed to impersonate.
  • Disable or remove any unused or legacy OAuth flows that rely on refresh tokens for impersonated sessions.
  • Log and alert on repeated or anomalous refresh token usage patterns to detect potential abuse.

Generated by OpenCVE AI on August 6, 2026 at 09:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wso2 identity Server
Vendors & Products Wso2 identity Server
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The user impersonation flow in WSO2 Identity Server fails to properly manage refresh tokens associated with impersonated sessions. This allows an attacker who has obtained an access token for an impersonated user to leverage the refresh token grant to obtain new access tokens, extending their ability to act as the legitimate user. An attacker who gains access to an impersonated user's access token can exploit this weakness to renew their authorization. This results in the continued ability to perform actions on behalf of the actual user, compromising log integrity and traceability by masking the true actor.
Title Improper Refresh Token Implementation via User Impersonation Flow in WSO2 Identity Server Enables Continued Unauthorized Actions
First Time appeared Wso2
Wso2 wso2 Carbon Oauth
Wso2 wso2 Identity Server
Weaknesses CWE-613
CPEs cpe:2.3:a:wso2:wso2_carbon_oauth:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*
Vendors & Products Wso2
Wso2 wso2 Carbon Oauth
Wso2 wso2 Identity Server
References
Metrics cvssV3_1

{'score': 2.4, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
WSO2
Published
Updated
Aug 6, 2026, 12:33 PM
Reserved
Nov 3, 2025, 8:28 AM
Status
Analyzed
Published
Aug 6, 2026, 8:16 AM
Modified
Sep 29, 2026, 2:10 PM