CVE-2024-7096
MEDIUMCVE-2024-7096 is a medium-severity (CVSS 5.4) CWE-863 vulnerability in org.wso2.am:am-parent. O3 Security confirms whether CVE-2024-7096 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
WSO2 products vulnerable to privilege escalation due to business logic flaw in SOAP admin services
Blast Radius
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.0 |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 5.2.0&&< 7.1.0 | 7.1.0 |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 CVE-2024-7096 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-7096 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-7096. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-7096 in your dependencies?
O3 detects CVE-2024-7096 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.