CVE Intelligence
Medium

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

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.

Published Jul 4, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: WSO2

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
WSO2
Api Manager and 4 more
CVSS base
5.3
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Manager, WSO2 Identity Server, WSO2 Identity Server As Key Manager…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
WSO2 Api Manager ≥ 3.1.0 and < 3.1.0.267≥ 3.2.0 and < 3.2.0.351≥ 4.0.0 and < 4.0.0.269≥ 4.1.0 and < 4.1.0.169≥ 3.0.0 and < 3.0.0.153 Vulnerable NIST National Vulnerability Database
WSO2 Api Manager ≥ 3.0.0 and < 3.0.0.153≥ 3.1.0 and < 3.1.0.267≥ 3.2.0 and < 3.2.0.351≥ 4.0.0 and < 4.0.0.269≥ 4.1.0 and < 4.1.0.169 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Identity Server ≥ 5.11.0 and < 5.11.0.321≥ 5.10.0 and < 5.10.0.284≥ 5.9.0 and < 5.9.0.138≥ 5.8.0 and < 5.8.0.101 Vulnerable NIST National Vulnerability Database
WSO2 Identity Server ≥ 5.11.0 and < 5.11.0.321≥ 5.10.0 and < 5.10.0.284≥ 5.9.0 and < 5.9.0.138≥ 5.8.0 and < 5.8.0.101 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Identity Server As Key Manager ≥ 5.9.0 and < 5.9.0.148≥ 5.10.0 and < 5.10.0.280 Vulnerable NIST National Vulnerability Database
WSO2 Identity Server As Key Manager ≥ 5.9.0 and < 5.9.0.148≥ 5.10.0 and < 5.10.0.280 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Open Banking Am ≥ 2.0.0 and < 2.0.0.313 Vulnerable NIST National Vulnerability Database
WSO2 Open Banking Am ≥ 2.0.0 and < 2.0.0.313 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Open Banking Iam ≥ 2.0.0 and < 2.0.0.333 Vulnerable NIST National Vulnerability Database
WSO2 Open Banking Iam ≥ 2.0.0 and < 2.0.0.333 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 3.1 Medium 3.9 1.4 nvd@nist.gov via NIST National Vulnerability Database
4.8 CVSS 3.1 Medium 2.2 2.5 ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
4.8 CVSS 3.1 Medium — — WSO2 via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 5.3 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-298

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · wso2/wso2 api manager, wso2/wso2 identity server, wso2/wso2 identity server as key manager, wso2/wso2 open banking am, w
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 5.3
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Jul 4, 2026 · WSO2

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

Elsewhere on this site

WSO2
every CVE for this vendor
CWE-298
other pages naming this weakness

Related CVEs (same products)

  • CVE-2024-8122 Potential brute force vulnerability due to non-expiring SMS OTPs 8d
  • CVE-2025-5802 Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery Sep 15, 2026
  • CVE-2025-13166 Username Enumeration via SMS OTP Flow in WSO2 Identity Server Allows User Account Discovery Sep 15, 2026
  • CVE-2026-4103 Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution Sep 14, 2026
  • CVE-2026-3096 Reverse Tabnabbing via New Tab Navigation in Multiple WSO2 Products Allows Phishing and Credential Theft Sep 10, 2026
  • CVE-2025-12737 Arbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution Sep 3, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2024-1248 is "Role Overwriting via Silent JIT Provisioning in Multiple WSO2 Products Enables Privilege Escalation", rated Medium. It affects Api Manager (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.