Skip to content
Fencer Intel
high 8.7

CVE-2026-2613 json

SQL Injection via Admin REST API in Multiple WSO2 Products Allows Database Information Inference and Service Disruption

published 7d ago modified 7d ago also EUVD-2026-115116

cvss
8.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

The Admin REST API accepts user-supplied input without adequately sanitizing it, allowing it to be included in the structure of SQL statements.

A user with administrator privileges can exploit this by influencing the structure of executed SQL statements, enabling blind SQL injection to infer database information and potentially impact the availability of the database service.

Patch / fix

  • WSO2 WSO2 API Manager 4.0.0.387, 4.1.0.251, 4.2.0.191, 4.3.0.102, 4.4.0.66, 4.5.0.51, 4.6.0.15
  • WSO2 WSO2 Traffic Manager 4.5.0.50, 4.6.0.15
  • WSO2 WSO2 API Control Plane 4.5.0.52, 4.6.0.16
  • WSO2 WSO2 Universal Gateway 4.5.0.51, 4.6.0.15
  • WSO2 WSO2 Carbon API Management Implementation 9.33.25

Is CVE-2026-2613 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7d ago

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H

Affected products

  • WSO2 WSO2 API Manager
  • WSO2 WSO2 Traffic Manager
  • WSO2 WSO2 API Control Plane
  • WSO2 WSO2 Universal Gateway
  • WSO2 WSO2 Carbon API Management Implementation

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.