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

> Attackers with management console access can bypass authorization to read versioned registry files, exposing sensitive configuration data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-w2r3-453h-7v25

## What is CVE-2024-3511?

CVE-2024-3511 is a medium-severity missing authorization vulnerability in Wso2 Api Manager, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-3511?

It affects 6 products.


Products: Wso2 Api Manager, Wso2 Enterprise Integrator, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam.

## How do I fix CVE-2024-3511?

No fix has been published for CVE-2024-3511 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-3511 being exploited?

There is no known exploitation of CVE-2024-3511 in the wild and no public exploit code.

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2022-29464](https://insights.sbomify.com/CVE-2022-29464/): WSO2 Multiple Products Unrestrictive Upload of File (critical 9.8, exploited in the wild)
- [CVE-2024-6914](https://insights.sbomify.com/CVE-2024-6914/): Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover (critical 9.8)
- [CVE-2020-13226](https://insights.sbomify.com/CVE-2020-13226/): WSO2 API Manager vulnerable to SSRF (critical 9.8)
- [CVE-2025-2905](https://insights.sbomify.com/CVE-2025-2905/): An XML External Entity (XXE) vulnerability in Multiple WSO2 Products (critical 9.1)
- [CVE-2021-42646](https://insights.sbomify.com/CVE-2021-42646/): XML external entity in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3511 and fix it if it is affected.

What it is: CVE-2024-3511 is a medium-severity missing authorization vulnerability in Wso2 Api Manager, published on 23 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3511 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3511/ (Markdown: https://insights.sbomify.com/CVE-2024-3511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3511
- OSV: https://osv.dev/vulnerability/CVE-2024-3511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3511/
Summaries are generated and may contain mistakes; the official description above is the record.