# CVE-2020-15594: Server-side request forgery in n/a

> An attacker can exploit the mail gateway configuration to scan for open ports and discover network machines, potentially exposing internal network details.

- **Severity:** Medium 4.3 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2020
- **Updated:** 30 May 2025
- **Also known as:** GHSA-wrf8-p6r2-xw72

## What is CVE-2020-15594?

CVE-2020-15594 is a medium-severity server-side request forgery vulnerability in n/a, published on 29 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An SSRF issue was discovered in Zoho Application Control Plus before version 10.0.511. The mail gateway configuration feature allows an attacker to perform a scan in order to discover open ports on a machine as well as available machines on the network segment on which the instance of the product is deployed.

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

## Which versions are affected by CVE-2020-15594?

It affects 1 product.


Products: Zohocorp Manageengine Application Control Plus.

## How do I fix CVE-2020-15594?

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

## Is CVE-2020-15594 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15595](https://insights.sbomify.com/CVE-2020-15595/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15594 and fix it if it is affected.

What it is: CVE-2020-15594 is a medium-severity server-side request forgery vulnerability in n/a, published on 29 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15594 in the wild and no public exploit code.

Affected product: n/a. 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-2020-15594/ (Markdown: https://insights.sbomify.com/CVE-2020-15594/index.md)
```

## Sources

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

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