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

Advisory record · `GHSA-j63j-7r7r-5v4j`

- **Identifiers:** `GHSA-j63j-7r7r-5v4j` · `CVE-2024-7096`
- **State:** Confirmed
- **Severity:** CVSS 4.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 30 May 2025
- **Updated:** 4 Jun 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 May 2025, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.wso2.am:am-parent` (Maven): affected `>=2.0.0, <4.4.0`; fixed in `4.4.0`
- `org.wso2.is:identity-server-parent` (Maven): affected `>=5.2.0, <7.1.0`; fixed in `7.1.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> WSO2 API Manager (org.wso2.am:am-parent) versions 2.0.0 up to 4.4.0 and WSO2 Identity Server (org.wso2.is:identity-server-parent) versions 5.2.0 up to 7.1.0 are affected by a privilege escalation flaw in SOAP admin services. An attacker with access to those services, who knows a custom role and an internal attribute used in the deployment, can create a user with elevated permissions. Upgrade am-parent to 4.4.0 or identity-server-parent to 7.1.0.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.2 Medium, CVSS 3.1: `CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`, from CNA (WSO2)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0074, the 55th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-j63j-7r7r-5v4j)

## Sources

- [GitHub Advisory Database: GHSA-j63j-7r7r-5v4j](https://github.com/advisories/GHSA-j63j-7r7r-5v4j)
- [OSV: GHSA-j63j-7r7r-5v4j](https://osv.dev/vulnerability/GHSA-j63j-7r7r-5v4j)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-7096>
- <https://github.com/wso2/docs-security/blob/cfd53689909eef62fc5427e193e35e7df8ab1ef8/en/docs/security-announcements/security-advisories/2024/WSO2-2024-3573.md>
- <https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3573>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-j63j-7r7r-5v4j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j63j-7r7r-5v4j/>. Everything for agents: <https://agentprime.io/llms.txt>.