Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-8325Improper Access Control via Gateway API in Multiple WSO2 Products Allows Unauthorized Operations

Description

The software fails to enforce role-based access controls for certain Gateway API invocations. Users with the 'Internal/Everyone' role can invoke these APIs, bypassing intended permission checks. This same vulnerability also affects Internal Service APIs, potentially exposing them in WSO2 APIM 3.x versions. A malicious actor with a valid user account on a vulnerable deployment can perform sensitive operations against the Gateway REST API regardless of their actual roles or privileges. This could lead to unintended behavior or misuse, particularly in production environments.

Timeline

  1. ID reserved

    By WSO2

  2. · 10 months later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-8325, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium6.3CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
NVDNVD · Analyzed3.1High8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.3.

Affected products

  • WSO2 · WSO2 API Control Plane

    • affected 4.5.0 – < 4.5.0.18

  • WSO2 · WSO2 Universal Gateway

    • affected 4.5.0 – < 4.5.0.17

  • WSO2 · WSO2 Traffic Manager

    • affected 4.5.0 – < 4.5.0.17

  • WSO2 · WSO2 API Manager

    • unknown < 3.2.0
    • affected 3.2.0 – < 3.2.0.435
    • affected 3.2.1 – < 3.2.1.55
    • affected 4.0.0 – < 4.0.0.355
    • affected 4.1.0 – < 4.1.0.219
    • affected 4.2.0 – < 4.2.0.157
    • affected 4.3.0 – < 4.3.0.70
    • affected 4.4.0 – < 4.4.0.33
    • affected 4.5.0 – < 4.5.0.17

  • WSO2 · WSO2 Carbon API Management Implementation

    • affected 6.7.206 – < 6.7.206.563
    • affected 6.7.210 – < 6.7.210.55
    • affected 9.0.174 – < 9.0.174.513
    • affected 9.20.74 – < 9.20.74.375
    • affected 9.28.116 – < 9.28.116.352
    • affected 9.29.120 – < 9.29.120.177
    • affected 9.30.67 – < 9.30.67.100
    • affected 9.31.86 – < 9.31.86.58
    • unaffected 9.32.75 – ≤ *

  • WSO2 · WSO2 Carbon API Manager Rest API Utility

    • affected 6.7.206 – < 6.7.206.563
    • affected 6.7.210 – < 6.7.210.55
    • affected 9.0.174 – < 9.0.174.513
    • affected 9.20.74 – < 9.20.74.375
    • affected 9.28.116 – < 9.28.116.352
    • affected 9.29.120 – < 9.29.120.177
    • affected 9.30.67 – < 9.30.67.100
    • affected 9.31.86 – < 9.31.86.58
    • unaffected 9.32.75 – ≤ *

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4401/#solution

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-8325 badge
[![CVE-2025-8325](https://cveledger.app/badge/CVE-2025-8325.svg)](https://cveledger.app/cve/CVE-2025-8325)

Record last updated .