WSO2 Identity Server Apps allows content spoofing in logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-6429: 0.21% estimated exploitation activity in the next 30 days; percentile 11.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A content spoofing issue exists in WSO2 Identity Server Apps, specifically in the Authentication Portal, due to improper handling of authentication error messages. When an authentication failure occurs, the portal previously accepted an authFailureMsg value supplied via URL and rendered it in the UI without validating it against the resource bundle. An attacker can craft a link that causes the portal to display attacker-controlled text in the error banner, enabling UI misrepresentation and social-engineering. The fix validates the message key against the resource bundle and encodes input before rendering. Upgrade to org.wso2.identity.apps:authentication-portal 2.4.4 or later to remediate.

Published by the source

23 Sep 2025, 18:30 UTC

Last modified by the source

27 Sep 2025, 03:29 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r6f3-55wj-g9p3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-6429

Advisory: WSO2 Identity Server Apps allows content spoofing in logs
IDs: CVE-2024-6429, GHSA-r6f3-55wj-g9p3
Record: https://patchnext.com/advisories/cve-2024-6429 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.wso2.identity.apps:authentication-portal 2.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.wso2.identity.apps:authentication-portal: affected < 2.4.4; fixed in 2.4.4

## Suggested inspection (read-only)
- Maven org.wso2.identity.apps:authentication-portal: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.wso2.identity.apps:authentication-portal.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r6f3-55wj-g9p3 (GitHub-reviewed advisory GHSA-r6f3-55wj-g9p3 lists affected ranges: Maven org.wso2.identity.apps:authentication-portal >=0 <2.4.4)

Commands are suggestions: review each one before running it.