NVD / CVE Program· CNA WSO2

CVE-2026-1728: Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access product-level Admin REST APIs. Exploitation of this vulnerability allows a low-privileged user to invoke the Admin REST APIs of WSO2 products, potentially leading to full administrative account takeover. This requires the attacker to already possess a low-privileged user account and be able to obtain a valid token for it.

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded

Pre-auth

Published: Aug 6, 2026
Updated: Aug 10, 2026
EPSS: 0.4% · 41th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · WSO2: 9.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
wso2	api control plane	cpe:2.3:a:wso2:api_control_plane
wso2	api manager	cpe:2.3:a:wso2:api_manager
wso2	traffic manager	cpe:2.3:a:wso2:traffic_manager
wso2	universal gateway	cpe:2.3:a:wso2:universal_gateway

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

wso2 api control plane4.5.0 and later · before 4.5.0.49
wso2 api control plane4.6.0 and later · before 4.6.0.13
wso2 api manager4.0.0 and later · before 4.0.0.384
wso2 api manager4.1.0 and later · before 4.1.0.248
wso2 api manager4.2.0 and later · before 4.2.0.188
wso2 api manager4.3.0 and later · before 4.3.0.99
wso2 api manager4.4.0 and later · before 4.4.0.63
wso2 api manager4.5.0 and later · before 4.5.0.48
wso2 api manager4.6.0 and later · before 4.6.0.12
wso2 traffic manager4.5.0 and later · before 4.5.0.47
wso2 traffic manager4.6.0 and later · before 4.6.0.12
wso2 universal gateway4.5.0 and later · before 4.5.0.48
wso2 universal gateway4.6.0 and later · before 4.6.0.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.49affected
- 4.6.0 and later · before 4.6.0.13affected
WSO2 WSO2 API Manager
- before 4.0.0unknown
- 4.0.0 and later · before 4.0.0.384affected
- 4.1.0 and later · before 4.1.0.248affected
- 4.2.0 and later · before 4.2.0.188affected
- 4.3.0 and later · before 4.3.0.99affected
- 4.4.0 and later · before 4.4.0.63affected
- 4.5.0 and later · before 4.5.0.48affected
- 4.6.0 and later · before 4.6.0.12affected
WSO2 WSO2 Carbon API Manager Rest API Common Functions
- 9.0.174 and later · before 9.0.174.550affected
- 9.28.116 and later · before 9.28.116.404affected
- 9.29.120 and later · before 9.29.120.221affected
- 9.30.67 and later · before 9.30.67.146affected
- 9.31.86 and later · before 9.31.86.130affected
- 9.32.147 and later · before 9.32.147.26affected
- 9.33.27 and laternot affected
WSO2 WSO2 Carbon API Manager Rest API Utility
- 9.20.74 and later · before 9.20.74.392affected
- 9.33.27 and laternot affected
WSO2 WSO2 Traffic Manager
- 4.5.0 and later · before 4.5.0.47affected
- 4.6.0 and later · before 4.6.0.12affected
WSO2 WSO2 Universal Gateway
- 4.5.0 and later · before 4.5.0.48affected
- 4.6.0 and later · before 4.6.0.12affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV
77This week
CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products
39Monitor
CVE-2025-9152Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-2445Jul 20, 2026 · Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Redirection and Modification
24Monitor
← EarlierCVE-2026-0637Aug 6, 2026 · Sensitive Information Disclosure via Event Publisher Logging in Multiple WSO2 Products
17Monitor
Later →CVE-2024-10302Aug 6, 2026 · Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

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

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

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

nvd-secondary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5077/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records