Is there a public exploit for CVE-2026-2613?

No public exploit for CVE-2026-2613 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-2613?

CVE-2026-2613 scores CVSS 8.7 (v3.1), rated high.

What does CVE-2026-2613 affect?

CVE-2026-2613 affects WSO2 WSO2 API Manager, WSO2 Traffic Manager, WSO2 API Control Plane, WSO2 Universal Gateway, WSO2 Carbon API Management Implementation.

8.7 High

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

CVE-2026-2613

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.

Assessment

CVSS: 8.7 (v3.1)
Severity: High
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 2 November 2026
Last updated: 2 November 2026
Affected: WSO2 · WSO2 API Control Plane · WSO2 API Manager · WSO2 Carbon API Management Implementation · WSO2 Traffic Manager
Assigner: WSO2

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H

At the source

EUVD (ENISA)

References

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

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 2 + 5? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-2613