# Multiple WSO2 products vulnerable to perform user impersonatoin using JIT provisioning

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

- **Identifiers:** `GHSA-f6jm-9pr8-9c3w` · `CVE-2023-6837`
- **State:** Confirmed
- **Severity:** CVSS 8.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 15 Dec 2023
- **Updated:** 2 Dec 2024
- **Reviewed by a person:** No

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.

## Affected packages

- `org.wso2.carbon.identity.framework:org.wso2.carbon.identity.application.authentication.framework` (Maven): affected `<5.20.254`; fixed in `5.20.254`
- `org.wso2.identity.apps:authentication-portal` (Maven): affected `<1.6.179.1`; fixed in `1.6.179.1`

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

- 8.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`, from 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

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f6jm-9pr8-9c3w)

## Sources

- [GitHub Advisory Database: GHSA-f6jm-9pr8-9c3w](https://github.com/advisories/GHSA-f6jm-9pr8-9c3w)
- [OSV: GHSA-f6jm-9pr8-9c3w](https://osv.dev/vulnerability/GHSA-f6jm-9pr8-9c3w)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-6837>
- <https://github.com/wso2/carbon-identity-framework/commit/fdab609760784086b8a3f55f7acf46d977a03d79>
- <https://github.com/wso2/identity-apps/commit/1424203bbe81688d661ea8b8cd28e332302e1c53>
- <https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2022/WSO2-2021-1573>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f6jm-9pr8-9c3w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f6jm-9pr8-9c3w/>. Everything for agents: <https://agentprime.io/llms.txt>.