CVEHit Business Advisory by IntegrityLab.ai
What’s the evidence?
Unauthorized administrative actions on WSO2 System REST APIs — CVE-2025-11969: Business Triage
The reported finding
- Required conditions
- An affected product below its own fix level, with System REST APIs a caller can reach.
- The caller's required privilege is unresolved:
- The advisory says "a user with low privileges".
- The CVE description says "users with lower privilege roles".
- The score says privileges required are none.
- The advisory says "Any APIs created and exposed through the WSO2 API Manager's API Gateway remain unaffected."
- Universal Gateway remains on its own row.
- Reported outcome
- Unauthorized administrative operations on the affected product, including executing administrative actions.
- The weakness is improper authorization, CWE-285: System REST APIs do not correctly enforce access control.
- WSO2's rating:
- Severity: critical.
- CVSS 3.1 base score: 9.4.
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L.
- The vector states:
- Access: network.
- Complexity: low.
- Privileges required: none.
- User interaction: none.
- Scope: unchanged.
- Confidentiality impact: high.
- Integrity impact: high.
- Availability impact: low.
- CISA's November 2, 2026 enrichment states:
- Exploitation: none.
- Automatable: yes.
- Technical impact: total.
- This is not a KEV listing.
- This does not prove attacks happened or did not happen.
- These sources describe possible harm, not an observed incident.
Fix guidance
- WSO2-2025-4733: subscription U2 level or higher for that base version, through WSO2 Updates
- API Manager 4.5.0 subscriptions use U2 level 32 or higher.
- Every other product and base version uses its own row in the first check.
- Community builds use the public fix linked from the advisory.
- If that public fix cannot be applied, migrate to the latest unaffected version of the same product.
- No universal replacement release is named.
- Versions before the first listed base version are unknown, not safe.
- WSO2 published the advisory on January 26, 2026. The CVE record was published on November 2, 2026.
- An installed fix does not settle earlier administrative changes.
What IntegrityLab.ai can check
- The authorized unauthenticated HTTP service-discovery path can record reachable web services and server identification returned in responses.
- That record is a clue for the customer's System owner.
- It is not proof of:
- The installed product.
- The package.
- The version.
- The update level.
- The configuration.
- No validated detection for CVE-2025-11969 was established by the supplied bounded code review.
- It does not identify System REST API reachability.
- It does not identify installed U2 updates.
- Service discovery does not establish that a private administrative endpoint was reached.
- What a response can establish is limited.
- An absent identifying response does not rule a product out.
- A front server can hide the backend.
- System owner: establish these facts from authorized internal records:
- The product.
- The version.
- Reachability.
- The update level.
Sources and vendor guidance
← Back to article questions