CVE-2024-7097: Incorrect Authorization in Multiple WSO2 Products via SOAP Admin Service Allowing Unauthorized User Signup
- Is it exploited?
Reported, not confirmed by CISA. VulnCheck KEV lists it as exploited in the wild. CISA has not added it to its Known Exploited Vulnerabilities catalog as of .
VulnCheck KEV lists it since . It cites 171 public reports, the first from . VulnCheck's own honeypots also recorded exploitation attempts.
- How likely is exploitation in the next 30 days?
- 0.7%
EPSS score, percentile 51.5 of all scored records. A probability estimated by FIRST, not a report of exploitation.
- How severe?
- 4.3 Medium
CVSS v3.1 base score, given by the CNA
- What should I do?
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3... … Full textSolution from the CVE record.
CISA has set no required action, because the vulnerability is not in KEV.
- Which versions are affected?
Affected
- from 1.3.0 to before 1.3.0.131
- from 1.4.0 to before 1.4.0.134
- from 1.5.0 to before 1.5.0.136
- from 2.0.0 to before 2.0.0.343
- from 1.3.0 to before 1.3.0.114
- from 1.4.0 to before 1.4.0.130
and 31 more in the table below
Source: CISA KEV 2026.10.29, as of ; VulnCheck KEV, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.
Description
Incorrect Authorization in Multiple WSO2 Products via SOAP Admin Service Allowing Unauthorized User Signup
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.
Source: CVE List, as of . About the data.
What to do
Advisories and patches
Solution (from the CVE record)
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3... https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3574/#solution
This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.
Affected products and versions
Versions by product, as listed in the CVE record (7 products)
| Status | Versions |
|---|---|
| Unknown | before 1.3.0 |
| Affected | from 1.3.0 to before 1.3.0.131 |
| Affected | from 1.4.0 to before 1.4.0.134 |
| Affected | from 1.5.0 to before 1.5.0.136 |
| Affected | from 2.0.0 to before 2.0.0.343 |
Versions not listed are: unaffected.
| Status | Versions |
|---|---|
| Unknown | before 1.3.0 |
| Affected | from 1.3.0 to before 1.3.0.114 |
| Affected | from 1.4.0 to before 1.4.0.130 |
| Affected | from 1.5.0 to before 1.5.0.120 |
Versions not listed are: unaffected.
| Status | Versions |
|---|---|
| Unknown | before 5.3.0 |
| Affected | from 5.3.0 to before 5.3.0.38 |
| Affected | from 5.5.0 to before 5.5.0.51 |
| Affected | from 5.6.0 to before 5.6.0.72 |
| Affected | from 5.7.0 to before 5.7.0.122 |
| Affected | from 5.9.0 to before 5.9.0.165 |
| Affected | from 5.10.0 to before 5.10.0.312 |
Versions not listed are: unaffected.
| Status | Versions |
|---|---|
| Unknown | before 2.0.0 |
| Affected | from 2.0.0 to before 2.0.0.29 |
| Affected | from 2.1.0 to before 2.1.0.39 |
| Affected | from 2.2.0 to before 2.2.0.56 |
| Affected | from 2.5.0 to before 2.5.0.83 |
| Affected | from 2.6.0 to before 2.6.0.142 |
| Affected | from 3.0.0 to before 3.0.0.162 |
| Affected | from 3.1.0 to before 3.1.0.294 |
| Affected | from 3.2.0 to before 3.2.0.384 |
| Affected | from 3.2.1 to before 3.2.1.16 |
| Affected | from 4.0.0 to before 4.0.0.305 |
| Affected | from 4.1.0 to before 4.1.0.166 |
Versions not listed are: unaffected.
And 2 more version entries in the CVE record.
| Status | Versions |
|---|---|
| Unknown | before 5.2.0 |
| Affected | from 5.2.0 to before 5.2.0.32 |
| Affected | from 5.3.0 to before 5.3.0.33 |
| Affected | from 5.4.0 to before 5.4.0.32 |
| Affected | from 5.4.1 to before 5.4.1.36 |
| Affected | from 5.5.0 to before 5.5.0.50 |
| Affected | from 5.6.0 to before 5.6.0.58 |
| Affected | from 5.7.0 to before 5.7.0.123 |
| Affected | from 5.8.0 to before 5.8.0.106 |
| Affected | from 5.9.0 to before 5.9.0.157 |
| Affected | from 5.10.0 to before 5.10.0.318 |
| Affected | from 5.11.0 to before 5.11.0.365 |
Versions not listed are: unaffected.
And 3 more version entries in the CVE record.
| Status | Versions |
|---|---|
| Unknown | before 2.0.0 |
| Affected | from 2.0.0 to before 2.0.0.364 |
Versions not listed are: unaffected.
| Status | Versions |
|---|---|
| Affected | from 2.2.0 to before 2.2.0.26 |
Versions not listed are: unknown.
Source: CVE List, as of . About the data.
Weakness
CWE-863
- CWE-863: Incorrect Authorization
CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.
Timeline
| Date | Event |
|---|---|
| CVE record published |
Known exploited WSO2 vulnerabilities
- CVE-2026-5430: WSO2 Multiple Products Path Traversal Vulnerability
- CVE-2022-29464: WSO2 Multiple Products Unrestrictive Upload of File Vulnerability