Content Spoofing via Error Handling in Multiple WSO2 Products Enables Social Engineering Attacks
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.1.49, 4.1.0.210, 4.2.0.148, 5.10.0.346, 5.11.0.385, and 2 more
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.2.1.49, 4.1.0.210, 4.2.0.148, 5.10.0.346, 5.11.0.385, or one of 2 more.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 11/100 · provisional
- Fix
- Fixed in 3.2.1.49, 4.1.0.210, 4.2.0.148, 5.10.0.346, 5.11.0.385, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
This vulnerability affects multiple WSO2 products, which are enterprise identity and API management software. Attackers can abuse the error handling in these products by injecting arbitrary content into error messages through URL parameters, which can be used to trick users into revealing credentials or taking harmful actions.
Read the original 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.
What to do
Upgrade to a fixed version: 3.2.1.49, 4.1.0.210, 4.2.0.148, 5.10.0.346, 5.11.0.385, or one of 2 more.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 API Manager
From 3.2.1 · fixed in 3.2.1.49; From 4.1.0 · fixed in 4.1.0.210; From 4.2.0 · fixed in 4.2.0.148
- WSO2 WSO2 Identity Server
From 5.10.0 · fixed in 5.10.0.346; From 5.11.0 · fixed in 5.11.0.385; From 6.0.0 · fixed in 6.0.0.229
- WSO2 WSO2 Identity Server as Key Manager
From 5.10.0 · fixed in 5.10.0.339
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.