Skip to main content
← Vulnerabilities

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

Requires an authenticated administrator on several WSO2 API, gateway and traffic products. Fixed in per-product builds such as API Manager 4.6.0.15 and Traffic Manager 4.6.0.15.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.0.387, 4.1.0.251, 4.2.0.191, 4.3.0.102, 4.4.0.66, and 6 more
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Attacker must be an authenticated user with administrator privileges. Affects WSO2 API Control Plane 4.6.0 and 4.5.0, WSO2 API Manager 4.6.0 through 4.0.0, WSO2 Traffic Manager 4.6.0 and 4.5.0, and WSO2 Universal Gateway 4.6.0 and 4.5.0.

Published
Last modified
Published
Not listed in CISA KEV
17/100 · provisional
Specific setups only
Fix
Fixed in 4.0.0.387, 4.1.0.251, 4.2.0.191, 4.3.0.102, 4.4.0.66, and 6 more
None on Exploit-DB, Metasploit or GitHub

Summary

This vulnerability affects multiple WSO2 products that expose the Admin REST API. It allows a user with administrator privileges to manipulate database queries, which could let them infer information stored in the database and potentially disrupt the availability of the database service.

Read the original description

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.

What to do

  • Check whether your setup matches what the bug needs.

    Attacker must be an authenticated user with administrator privileges. Affects WSO2 API Control Plane 4.6.0 and 4.5.0, WSO2 API Manager 4.6.0 through 4.0.0, WSO2 Traffic Manager 4.6.0 and 4.5.0, and WSO2 Universal Gateway 4.6.0 and 4.5.0.
  • Upgrade to a fixed version: 4.0.0.387, 4.1.0.251, 4.2.0.191, 4.3.0.102, 4.4.0.66, or one of 6 more.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • WSO2 WSO2 API Manager

    From 4.0.0 · fixed in 4.0.0.387; From 4.1.0 · fixed in 4.1.0.251; From 4.2.0 · fixed in 4.2.0.191; From 4.3.0 · fixed in 4.3.0.102; From 4.4.0 · fixed in 4.4.0.66; From 4.5.0 · fixed in 4.5.0.51; From 4.6.0 · fixed in 4.6.0.15

  • WSO2 WSO2 Traffic Manager

    From 4.5.0 · fixed in 4.5.0.50; From 4.6.0 · fixed in 4.6.0.15

  • WSO2 WSO2 API Control Plane

    From 4.5.0 · fixed in 4.5.0.52; From 4.6.0 · fixed in 4.6.0.16

  • WSO2 WSO2 Universal Gateway

    From 4.5.0 · fixed in 4.5.0.51; From 4.6.0 · fixed in 4.6.0.15

  • org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.impl

    fixed in 9.33.25

Evidence 1

  1. Advisory

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-2613

What does this mean?

An administrator can send crafted input to the admin REST API that changes the structure of SQL statements the product runs. This blind SQL injection lets them infer database information, and it may also impact the availability of the database service.Source: security.docs.wso2.com

Am I affected, and how do I check?

The affected ranges are API Manager 4.0.0 through 4.6.0 builds below each listed fix, Traffic Manager 4.5.0 and 4.6.0 builds below 4.5.0.50 and 4.6.0.15, API Control Plane builds below 4.5.0.52 and 4.6.0.16, Universal Gateway builds below 4.5.0.51 and 4.6.0.15, and Carbon API Management builds below 9.33.25. Compare the installed build number against these ranges.Source: security.docs.wso2.com

What should I do about it?

Upgrade to the fixed build for the product and release line, such as 4.6.0.16 for WSO2 API Control Plane or 9.33.25 for WSO2 Carbon API Management.Source: security.docs.wso2.com

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data