Content Spoofing in Multiple WSO2 Products via Error Message Injection
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in API Manager 3.2.0.409, API Manager 3.2.1.33, API Manager 4.0.0.327 and 10 more.
A content spoofing vulnerability exists in multiple WSO2 products due to improper error message handling. Under certain conditions, error messages are passed through URL parameters without validation, allowing malicious actors to inject arbitrary content into the UI. By exploiting this vulnerability, attackers can manipulate browser-displayed error messages, enabling social engineering attacks through deceptive or misleading content.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| WSO2 | API Manager | =3.2.0, =3.2.1, =4.0.0, =4.1.0, =4.2.0, =4.3.0, =4.4.0, >=3.2.0 <3.2.0.409, >=3.2.1 <3.2.1.33, >=4.0.0 <4.0.0.327, >=4.1.0 <4.1.0.188, >=4.2.0 <4.2.0.128, >=4.3.0 <4.3.0.38, >=4.4.0 <4.4.0.4 | 3.2.0.409, 3.2.1.33, 4.0.0.327, 4.1.0.188, 4.2.0.128, 4.3.0.38, 4.4.0.4 |
| WSO2 | Identity Server | >=5.10.0 <5.10.0.314, >=5.11.0 <5.11.0.359, >=6.0.0 <6.0.0.203, >=6.1.0 <6.1.0.176, =5.10.0, =5.11.0, =6.0.0, =6.1.0, =7.0.0, >=7.0.0 <7.0.0.48, >=5.10.0 <5.10.0.338 | 5.10.0.314, 5.11.0.359, 6.0.0.203, 6.1.0.176, 7.0.0.48, 5.10.0.338 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in WSO2, strongest first
Embed
A live severity badge for an advisory, README or ticket