Skip to content

WSO2 products vulnerable to privilege escalation due to business logic flaw in SOAP admin services

Moderate severity GitHub Reviewed Published May 30, 2025 to the GitHub Advisory Database • Updated Jun 4, 2025

Package

maven org.wso2.am:am-parent (Maven)

Affected versions

>= 2.0.0, <= 4.3.0

Patched versions

4.4.0
maven org.wso2.is:identity-server-parent (Maven)
>= 5.2.0, <= 7.0.0
7.1.0

Description

A privilege escalation vulnerability exists in multiple WSO2 products due to a business logic flaw in SOAP admin services. A malicious actor can create a new user with elevated permissions only when all of the following conditions are met:

  • SOAP admin services are accessible to the attacker.
  • The deployment includes an internally used attribute that is not part of the default WSO2 product configuration.
  • At least one custom role exists with non-default permissions.
  • The attacker has knowledge of the custom role and the internal attribute used in the deployment.

Exploiting this vulnerability allows malicious actors to assign higher privileges to self-registered users, bypassing intended access control mechanisms.

References

Published by the National Vulnerability Database May 30, 2025
Published to the GitHub Advisory Database May 30, 2025
Reviewed Jun 4, 2025
Last updated Jun 4, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(2nd percentile)

Weaknesses

CVE ID

CVE-2024-7096

GHSA ID

GHSA-j63j-7r7r-5v4j

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.