CVE-2024-3511 | Incorrect Authorization in Multiple WSO2 Products Allows Unauthorized Access to Registry Versioned Files

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.

Published: 2025-06-23 Last update: 2025-10-06 Assigner: ed10eef1-636d-4fbe-9993-6890dfa878f8 Source: ed10eef1-636d-4fbe-9993-6890dfa878f8

Conclusion & alert: CVE-2024-3511 is rated Low Risk (29.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.14%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-3511

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-19 0.01% 0.14% +0.13%
2 2025-06-23 0.01%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-3511

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 ed10eef1-636d-4fbe-9993-6890dfa878f8

Weakness enumeration for CVE-2024-3511

Affected software / configurations for CVE-2024-3511

Vendor Product Version Raw CPE
wso2 api_manager 3.2.0 cpe:2.3:a:wso2:api_manager:3.2.0:*:*:*:*:*:*:*
wso2 api_manager 3.2.1 cpe:2.3:a:wso2:api_manager:3.2.1:*:*:*:*:*:*:*
wso2 api_manager 4.0.0 cpe:2.3:a:wso2:api_manager:4.0.0:*:*:*:*:*:*:*
wso2 api_manager 4.1.0 cpe:2.3:a:wso2:api_manager:4.1.0:-:*:*:*:*:*:*
wso2 api_manager 4.2.0 cpe:2.3:a:wso2:api_manager:4.2.0:-:*:*:*:*:*:*
wso2 api_manager 4.3.0 cpe:2.3:a:wso2:api_manager:4.3.0:-:*:*:*:*:*:*
wso2 enterprise_integrator 6.6.0 cpe:2.3:a:wso2:enterprise_integrator:6.6.0:*:*:*:*:*:*:*
wso2 identity_server 5.10.0 cpe:2.3:a:wso2:identity_server:5.10.0:*:*:*:*:*:*:*
wso2 identity_server 5.11.0 cpe:2.3:a:wso2:identity_server:5.11.0:*:*:*:*:*:*:*
wso2 identity_server 6.0.0 cpe:2.3:a:wso2:identity_server:6.0.0:*:*:*:*:*:*:*
wso2 identity_server 6.1.0 cpe:2.3:a:wso2:identity_server:6.1.0:*:*:*:*:*:*:*
wso2 identity_server 7.0.0 cpe:2.3:a:wso2:identity_server:7.0.0:*:*:*:*:*:*:*
wso2 identity_server_as_key_manager 5.10.0 cpe:2.3:a:wso2:identity_server_as_key_manager:5.10.0:*:*:*:*:*:*:*
wso2 open_banking_am 2.0.0 cpe:2.3:a:wso2:open_banking_am:2.0.0:*:*:*:*:*:*:*
wso2 open_banking_iam 2.0.0 cpe:2.3:a:wso2:open_banking_iam:2.0.0:*:*:*:*:*:*:*

References for CVE-2024-3511

cvelogic Threat Intelligence