Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-f6jm-9pr8-9c3w

Multiple WSO2 products vulnerable to perform user impersonatoin using JIT provisioning

CVSS 8.5 HighEPSS 0.0046 · 40th percentile

Published by the GitHub Advisory Database at 15 Dec 2023, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.frameworkMaven<5.20.2545.20.254
org.wso2.identity.apps:authentication-portalMaven<1.6.179.11.6.179.1
Identifiers
GHSA-f6jm-9pr8-9c3w · CVE-2023-6837
Weakness (CWE)
CWE-863
Tags
Published
15 Dec 2023
Updated
2 Dec 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Two WSO2 packages are affected: org.wso2.carbon.identity.framework's authentication framework before 5.20.254, and the authentication-portal package before 1.6.179.1. An attacker needs a fresh, unused account at a federated identity provider configured for JIT provisioning, plus the username of a valid local user, and the affected service provider must have the "Assert identity using mapped local subject identifier" option enabled. Under those conditions, the attacker can impersonate the local user through the JIT provisioning flow. Upgrade to 5.20.254 or 1.6.179.1 or later.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N CNA (WSO2)
  • CISA KEV Not listed.
  • EPSS 0.0046, the 40th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.