# CVE-2019-6512: Server-side request forgery in n/a

> Attackers can exploit WSO2 API Manager to perform server-side request forgery, enabling internal port scanning and file enumeration.

- **Severity:** Medium 4.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2019
- **Updated:** 30 May 2025
- **Also known as:** GHSA-h4w8-wwg9-q6pr

## What is CVE-2019-6512?

CVE-2019-6512 is a medium-severity server-side request forgery vulnerability in Wso2 Api Manager, published on 14 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in WSO2 API Manager 2.6.0. It is possible to force the application to perform requests to the internal workstation (SSRF port-scanning), other adjacent workstations (SSRF network scanning), or to enumerate files because of the existence of the file:// wrapper.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-6512?

It affects 1 product.


Products: Wso2 Api Manager.

## How do I fix CVE-2019-6512?

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

## Is CVE-2019-6512 being exploited?

There is no known exploitation of CVE-2019-6512 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-2019-6512 and fix it if it is affected.

What it is: CVE-2019-6512 is a medium-severity server-side request forgery vulnerability in Wso2 Api Manager, published on 14 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6512 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-2019-6512/ (Markdown: https://insights.sbomify.com/CVE-2019-6512/index.md)
```

## Sources

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

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