Skip to content
Fencer Intel
medium 4.3

CVE-2024-6429 json

Content Spoofing in Multiple WSO2 Products via Error Message Injection

published last yr. modified 2d ago also EUVD-2024-55023 , GHSA-r6f3-55wj-g9p3

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.wso2.identity.apps:authentication-portal 2.4.4
  • WSO2 WSO2 Identity Server as Key Manager 5.10.0.338
  • WSO2 WSO2 API Manager 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 WSO2 Identity Server 5.10.0.314, 5.11.0.359, 6.0.0.203, 6.1.0.176, 7.0.0.48

Is CVE-2024-6429 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.wso2.identity.apps:authentication-portal
<2.4.4
2.4.4

Affected products

  • WSO2 WSO2 Identity Server as Key Manager
  • WSO2 WSO2 API Manager
  • WSO2 WSO2 Identity Server

Classification

Weakness
  • CWE-451 User Interface (UI) Misrepresentation of Critical Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.