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

CVE-2024-3511

Incorrect Authorization in Multiple WSO2 Products Allows Unauthorized Access to Registry Versioned Files

Medium4.3EPSS 0.21%
Published
Updated
Reserved
Assigned by
WSO2

Description

An incorrect authorization vulnerability exists in multiple WSO2 products that allows unauthorized access to versioned files stored in the registry. Due to flawed authorization logic, a malicious actor with access to the management console can exploit a specific bypass method to retrieve versioned files without proper authorization. Successful exploitation of this vulnerability could lead to unauthorized disclosure of configuration or resource files that may be stored as registry versions, potentially aiding further attacks or system reconnaissance.

Timeline

  1. ID reserved

    By WSO2

  2. · 15 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-2024-3511, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium4.3CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVDNVD · Analyzed3.1Medium4.3CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (8 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 4.3.

Weakness

Affected products

  • WSO2 · WSO2 Enterprise Integrator

    • unknown < 6.6.0
    • affected 6.6.0 – < 6.6.0.205
  • WSO2 · WSO2 API Manager

    • unknown < 3.1.0
    • affected 3.1.0 – < 3.1.0.273
    • affected 3.2.0 – < 3.2.0.361
    • affected 3.2.1 – < 3.2.1.13
    • affected 4.0.0 – < 4.0.0.306
    • affected 4.1.0 – < 4.1.0.163
    • affected 4.2.0 – < 4.2.0.98
    • affected 4.3.0 – < 4.3.0.17
  • WSO2 · WSO2 Identity Server as Key Manager

    • unknown < 5.10.0
    • affected 5.10.0 – < 5.10.0.289
  • WSO2 · WSO2 Identity Server

    • unknown < 5.10.0
    • affected 5.10.0 – < 5.10.0.292
    • affected 5.11.0 – < 5.11.0.333
    • affected 6.0.0 – < 6.0.0.180
    • affected 6.1.0 – < 6.1.0.141
    • affected 7.0.0 – < 7.0.0.8
  • WSO2 · WSO2 Open Banking AM

    • unknown < 2.0.0
    • affected 2.0.0 – < 2.0.0.320
  • WSO2 · WSO2 Open Banking IAM

    • unknown < 2.0.0
    • affected 2.0.0 – < 2.0.0.341
  • WSO2 · WSO2 Carbon User Manager Kernel

    • affected 4.5.0 – < 4.5.0.5
    • affected 4.5.3 – < 4.5.3.35
    • affected 4.6.0 – < 4.6.0.140
    • affected 4.6.1 – < 4.6.1.107
    • affected 4.6.2 – < 4.6.2.323
    • affected 4.6.3 – < 4.6.3.18
    • affected 4.6.4 – < 4.6.4.3
    • affected 4.7.1 – < 4.7.1.47
    • affected 4.8.1 – < 4.8.1.19
    • affected 4.9.0 – < 4.9.0.52
    • affected 4.9.26 – < 4.9.26.10
    • affected 4.10.9 – < 4.10.9.8
    • unaffected 4.10.13 – ≤ *

What to do

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

References (1)

Sources

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

Badge for a README or a ticket

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

Record last updated .