Skip to main content
VulnerabilityPublished Updated

CVE-2024-1248: WSO2 API Manager · Improper Handling of Identity During Provisioning

Affects WSO2 API ManagerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium · fixed in 4.1.0.169 : update WSO2 API Manager when convenient.

Data as of 15 Nov 2026, 20:24 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.0.169, 4.0.0.269, 3.2.0.351 +10
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
WSO2WSO2 API ManagerAffected
  • >=4.1.0 <4.1.0.169
Fixed in
  • 4.1.0.169
WSO2WSO2 API ManagerAffected
  • >=4.0.0 <4.0.0.269
Fixed in
  • 4.0.0.269
WSO2WSO2 API ManagerAffected
  • >=3.2.0 <3.2.0.351
Fixed in
  • 3.2.0.351
WSO2WSO2 API ManagerAffected
  • >=3.1.0 <3.1.0.267
Fixed in
  • 3.1.0.267
WSO2WSO2 API ManagerAffected
  • >=3.0.0 <3.0.0.153
Fixed in
  • 3.0.0.153
WSO2WSO2 Identity ServerAffected
  • >=5.11.0 <5.11.0.321
Fixed in
  • 5.11.0.321

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, organizations should review their federated IDP configurations, especially the roles assigned during silent JIT provisioning, to minimize privilege escalation risks. Consider disabling silent JIT provisioning if feasible or implementing additional controls to segregate local and federated user roles.

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.

References

Community reviews

Loading reviews…