WSO2 products vulnerable to privilege escalation due to business logic flaw in SOAP admin servicesGHSA-j63j-7r7r-5v4j
MEDIUMGHSA-j63j-7r7r-5v4j is a medium-severity (CVSS 4.2) CWE-863 vulnerability in org.wso2.am:am-parent. A fix is available for org.wso2.am:am-parent — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j63j-7r7r-5v4j.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.wso2.am:am-parent☕org.wso2.is:identity-server-parentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wso2.am:am-parent | ≥ 2.0.0&&< 4.4.0 | 4.4.0org.wso2.am:am-parent:4.4.0 |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 5.2.0&&< 7.1.0 | 7.1.0org.wso2.is:identity-server-parent:7.1.0 |
Affected Products
api managerwso2identity serverwso2identity server as key managerwso2open banking amwso2open banking iamwso2open banking kmwso2Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.am:am-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wso2.am:am-parent to 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j63j-7r7r-5v4j is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-j63j-7r7r-5v4j in your dependencies?
Find it across Maven, including transitive dependencies.