VulnerabilityPublished 30 May 2025

CVE-2024-7097: WSO2 Open Banking AM · Incorrect Authorization

Affects WSO2 Open Banking AMSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 May 2025
Detectable: evidence found.
nuclei template: WSO2 User Registration - Arbitrary Account Creation
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.wso2/open-banking-am`pkg:maven/org.wso2/open-banking-am`Other threats	Affected 1.3.0 – 2.0.0 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Restrict network access to the SOAP admin service to trusted internal IP ranges only, using firewall rules or network segmentation to prevent external or unauthorized access. 2) Implement strict monitoring and alerting on user account creation events, focusing on unusual spikes or patterns indicative of mass account creation attempts. 3) Enforce additional application-layer authorization checks where possible, such as integrating with external identity governance tools to validate account creation requests. 4) Temporarily disable or limit self-registration features if feasible until a patch is available. 5) Conduct regular audits of user accounts to identify and remove unauthorized or suspicious accounts promptly. 6) Engage with WSO2 support or community channels to obtain updates on patches or workarounds. 7) Employ rate limiting or throttling mechanisms on the SOAP admin service endpoints to mitigate resource exhaustion risks. These targeted actions go beyond generic advice by focusing on access control hardening, monitoring, and operational controls specific to the vulnerability's exploitation vector.

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.

Impact

For European organizations, especially those in the financial sector leveraging WSO2 Open Banking AM, this vulnerability poses a risk of unauthorized access through the creation of illegitimate user accounts. Although the accounts are low-privileged, they could be used for lateral movement, reconnaissance, or as a foothold for further exploitation. The ability to create multiple accounts without authorization could also lead to resource exhaustion, potentially disrupting service availability. This is particularly concerning for banks and financial institutions subject to strict regulatory requirements such as PSD2 and GDPR, where unauthorized access and data integrity issues can lead to compliance violations, reputational damage, and financial penalties. Additionally, the vulnerability could be exploited to bypass self-registration controls, undermining customer onboarding processes and potentially enabling fraud or identity misuse. The medium severity rating suggests that while the immediate impact on confidentiality and availability is limited, the integrity and trustworthiness of the system are compromised, which is critical in the financial domain.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3574/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 14:55 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats