VulnerabilityPublished 2 Nov 2026

CVE-2024-12139: WSO2 API Manager · Content Spoofing via Error Handling

Affects WSO2 API ManagerSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium · fixed in 4.2.0.148 : update WSO2 API Manager when convenient.

Data as of 2 Nov 2026, 19:28 UTC

CVSS 3.1 base score

4.3Medium

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	4.3

Patch: Available – fixed in 4.2.0.148, 4.1.0.210, 3.2.1.49 +4

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
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: 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 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
WSO2WSO2 API Manager	Affected >=4.2.0 <4.2.0.148	Fixed in 4.2.0.148
WSO2WSO2 API Manager	Affected >=4.1.0 <4.1.0.210	Fixed in 4.1.0.210
WSO2WSO2 API Manager	Affected >=3.2.1 <3.2.1.49	Fixed in 3.2.1.49
WSO2WSO2 Identity Server	Affected >=6.0.0 <6.0.0.229	Fixed in 6.0.0.229
WSO2WSO2 Identity Server	Affected >=5.11.0 <5.11.0.385	Fixed in 5.11.0.385
WSO2WSO2 Identity Server	Affected >=5.10.0 <5.10.0.346	Fixed in 5.10.0.346

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

AI-suggested

Fixed versions addressing this vulnerability have been released for all affected versions of WSO2 API Manager. Users should upgrade to the respective fixed versions: 3.2.1.49, 4.1.0.210, 4.2.0.148, 5.10.0.346, 5.10.0.339, 5.11.0.385, or 6.0.0.229. Applying these official fixes is the recommended remediation. No additional vendor advisory indicates alternative mitigations or that no action is required.

Description

The error handling implementation fails to properly sanitize or validate user-supplied input within URL parameters under specific conditions. This allows end-users to manipulate the error messages that are displayed by the application. By exploiting this vulnerability, malicious actors can inject arbitrary content into error messages. This enables them to perform social engineering attacks, such as phishing or credential theft, by replacing legitimate error messages with malicious content, misleading users into compromising sensitive information or taking harmful actions.

Impact

The vulnerability does not allow direct compromise of confidentiality or availability but enables attackers to perform social engineering attacks through content spoofing in error messages. This can lead to users being misled into divulging sensitive information or performing harmful actions. The CVSS score of 4.3 reflects a medium impact primarily on integrity via user interaction.

Summary

The vulnerability in WSO2 API Manager involves improper sanitization or validation of user-supplied input within URL parameters in the error handling mechanism. This allows an attacker to manipulate error messages displayed by the application by injecting arbitrary content. Such manipulation can be leveraged to conduct social engineering attacks, including phishing and credential theft, by presenting users with deceptive error messages that appear legitimate. Multiple versions of WSO2 API Manager are affected, with fixes released in versions 3.2.1.49, 4.1.0.210, 4.2.0.148, 5.10.0.346, 5.10.0.339, 5.11.0.385, and 6.0.0.229.

CWE-116Improper Encoding or Escaping of Output (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
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.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Implementation
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
Query Parameterization (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
V14.4.2 (opens in a new tab)
Attack patterns
Cross Zone Scripting (opens in a new tab)
User-Controlled Filename (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
AJAX Footprinting (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/2026/WSO2-2024-3805/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Nov 2026, 17:45 UTC

WeaknessesCWE-116

Technical details

References

Community reviews

Related threats