VulnerabilityPublished 2 Nov 2026

CVE-2024-2372: The affected components accept user-supplied input for constructing redirection URLs without enforcing

Source GCVE Database

Compare

Authoritative record:CVE-2024-2372· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.0.0.383 when convenient.

Data as of 2 Nov 2026, 13:31 UTC

CVSS 3.1 base score

5.4Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (WSO2)	CVSS 3.1	5.4

Patch: Available – fixed in 2.0.0.383, 4.3.0.59, 4.2.0.146 +28

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to 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 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 2 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-9vv9-3fcf-65rq

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
WSO2WSO2 Open Banking AM	Affected >=2.0.0 <2.0.0.383	Fixed in 2.0.0.383
WSO2WSO2 API Manager	Affected >=4.3.0 <4.3.0.59	Fixed in 4.3.0.59
WSO2WSO2 API Manager	Affected >=4.2.0 <4.2.0.146	Fixed in 4.2.0.146
WSO2WSO2 API Manager	Affected >=4.1.0 <4.1.0.208	Fixed in 4.1.0.208
WSO2WSO2 API Manager	Affected >=4.0.0 <4.0.0.310	Fixed in 4.0.0.310
WSO2WSO2 API Manager	Affected >=3.2.1 <3.2.1.51	Fixed in 3.2.1.51

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

AI-suggested

Since the vulnerability involves improper validation of redirect URLs, mitigation typically involves implementing strict validation or whitelisting of redirect destinations. Monitor vendor advisories for any forthcoming patches or official remediation guidance.

Description

CVE-2024-2372 is an open redirection vulnerability where affected components accept user input for redirection URLs without proper validation. This flaw allows attackers to craft URLs that redirect users to arbitrary external domains, facilitating phishing attacks through social engineering.

Impact

Successful exploitation can lead to users being redirected to malicious external websites, increasing the risk of phishing attacks and potential credential theft or other social engineering harms. The vulnerability has a CVSS 3.1 base score of 5.4 (medium severity), indicating limited confidentiality and integrity impact with no availability impact.

Summary

The vulnerability arises because certain components do not enforce validation constraints on user-supplied input used to construct redirection URLs. An attacker can exploit this by creating malicious links that redirect users to attacker-controlled sites. This open redirection can be leveraged to deceive users into disclosing sensitive information or performing unintended actions.

CWE-601URL Redirection to Untrusted Site (Open Redirect) (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Nov 2026, 13:31 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats