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

> An SSRF vulnerability in CRMEB allows attackers to download arbitrary files and execute code remotely on the server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2020
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-vm4j-2mrw-2c59

## What is CVE-2020-25466?

CVE-2020-25466 is a critical server-side request forgery vulnerability in n/a, published on 23 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SSRF vulnerability exists in the downloadimage interface of CRMEB 3.0, which can remotely download arbitrary files on the server and remotely execute arbitrary code.

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

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

It affects 1 product.


Products: Crmeb Crmeb.

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

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

## Is CVE-2020-25466 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-25763](https://insights.sbomify.com/CVE-2025-25763/): SQL injection in n/a (critical 9.8)
- [CVE-2023-30185](https://insights.sbomify.com/CVE-2023-30185/): File upload in n/a (critical 9.8)
- [CVE-2020-21787](https://insights.sbomify.com/CVE-2020-21787/): File upload in n/a (critical 9.8)
- [CVE-2020-21394](https://insights.sbomify.com/CVE-2020-21394/): SQL injection in n/a (high 8.8)
- [CVE-2024-52726](https://insights.sbomify.com/CVE-2024-52726/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25466 is a critical server-side request forgery vulnerability in n/a, published on 23 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25466 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-25466/ (Markdown: https://insights.sbomify.com/CVE-2020-25466/index.md)
```

## Sources

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

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