# CVE-2024-7097: Incorrect Authorization in Multiple WSO2 Products via SOAP Admin Service Allowing Unauthorized User Signup

> Attackers can bypass self-registration settings to create unauthorized user accounts, potentially leading to privilege escalation or resource exhaustion.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-2vx2-pv2m-vwrq

## What is CVE-2024-7097?

CVE-2024-7097 is a medium-severity missing authorization vulnerability in Wso2 Api Manager, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An incorrect authorization vulnerability exists in multiple WSO2 products due to a flaw in the SOAP admin service, which allows user account creation regardless of the self-registration configuration settings. This vulnerability enables malicious actors to create new user accounts without proper authorization.

Exploitation of this flaw could allow an attacker to create multiple low-privileged user accounts, gaining unauthorized access to the system. Additionally, continuous exploitation could lead to system resource exhaustion through mass user creation.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-7097?

It affects 6 products.


Products: Wso2 Api Manager, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam, Wso2 Open Banking Km.

## How do I fix CVE-2024-7097?

No fix has been published for CVE-2024-7097 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-7097 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-7097 exists.

Public exploit code:

- WSO2 User Registration - Arbitrary Account Creation (nuclei): http/cves/2024/CVE-2024-7097.yaml

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2022-29464](https://insights.sbomify.com/CVE-2022-29464/): WSO2 Multiple Products Unrestrictive Upload of File (critical 9.8, exploited in the wild)
- [CVE-2024-6914](https://insights.sbomify.com/CVE-2024-6914/): Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover (critical 9.8)
- [CVE-2020-13226](https://insights.sbomify.com/CVE-2020-13226/): WSO2 API Manager vulnerable to SSRF (critical 9.8)
- [CVE-2025-2905](https://insights.sbomify.com/CVE-2025-2905/): An XML External Entity (XXE) vulnerability in Multiple WSO2 Products (critical 9.1)
- [CVE-2021-42646](https://insights.sbomify.com/CVE-2021-42646/): XML external entity in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7097 and fix it if it is affected.

What it is: CVE-2024-7097 is a medium-severity missing authorization vulnerability in Wso2 Api Manager, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-7097 exists.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-7097/ (Markdown: https://insights.sbomify.com/CVE-2024-7097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7097
- OSV: https://osv.dev/vulnerability/CVE-2024-7097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-7097/
Summaries are generated and may contain mistakes; the official description above is the record.