CVE Intelligence
Critical Privilege escalation

CVE-2026-1728 — Improper Privilege Management in WSO2 Api Control Plane

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.

Published Aug 6, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database · CNA: ed10eef1-636d-4fbe-9993-6890dfa878f8

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
WSO2
Api Control Plane and 3 more
CVSS base
9.8
Critical · 1 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Control Plane, WSO2 Api Manager, WSO2 Traffic Manager…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (privilege escalation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
WSO2 Api Control Plane ≥ 4.5.0 and < 4.5.0.49≥ 4.6.0 and < 4.6.0.13 Vulnerable NIST National Vulnerability Database
WSO2 Api Manager ≥ 4.0.0 and < 4.0.0.384≥ 4.1.0 and < 4.1.0.248≥ 4.2.0 and < 4.2.0.188≥ 4.3.0 and < 4.3.0.99≥ 4.4.0 and < 4.4.0.63≥ 4.5.0 and < 4.5.0.48≥ 4.6.0 and < 4.6.0.12 Vulnerable NIST National Vulnerability Database
WSO2 Traffic Manager ≥ 4.5.0 and < 4.5.0.47≥ 4.6.0 and < 4.6.0.12 Vulnerable NIST National Vulnerability Database
WSO2 Universal Gateway ≥ 4.5.0 and < 4.5.0.48≥ 4.6.0 and < 4.6.0.12 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

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

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-269 · Improper Privilege Management

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • CVSS changed · 9.8
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Aug 6, 2026 · ed10eef1-636d-4fbe-9993-6890dfa878f8

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

Elsewhere on this site

WSO2
every CVE for this vendor
CWE-269
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2025-12737 OS Command Injection in WSO2 Api Control Plane Sep 3, 2026
  • High CVE-2026-3416 Use of Insufficiently Random Values in WSO2 Api Control Plane Sep 3, 2026
  • Critical CVE-2026-5430 WSO2 Multiple Products Path Traversal Vulnerability KEV Aug 6, 2026
  • Critical CVE-2025-15039 The Conditional Authentication (Adaptive Authentication) script does not correctly… Aug 6, 2026
  • Medium CVE-2026-0637 Insertion of Sensitive Information into Log File in WSO2 Api Control Plane Aug 6, 2026
  • Medium CVE-2025-13394 Cross-Site Request Forgery (CSRF) in WSO2 Api Control Plane Aug 6, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-1728 is "Improper Privilege Management in WSO2 Api Control Plane", rated Critical. It affects Api Control Plane (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.