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

> An unauthenticated attacker can exploit a blind SSRF vulnerability in the Canto WordPress plugin to make requests to internal and external servers.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-425j-2mfw-73xx

## What is CVE-2020-28978?

CVE-2020-28978 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Canto plugin 1.3.0 for WordPress contains blind SSRF vulnerability. It allows an unauthenticated attacker can make a request to any internal and external server via /includes/lib/tree.php?subdomain=SSRF.

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

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

It affects 1 product.


Products: Canto Canto.

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

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

## Is CVE-2020-28978 being exploited?

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

Public exploit code:

- Wordpress Plugin Canto 1.3.0 - Blind SSRF (Unauthenticated) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-25096](https://insights.sbomify.com/CVE-2024-25096/): WordPress canto plugin <= 3.0.7 - Unauth. Remote Code Execution (RCE) vulnerability (critical 10.0)
- [CVE-2024-4936](https://insights.sbomify.com/CVE-2024-4936/): Canto <= 3.0.8 - Unauthenticated Remote File Inclusion (critical 9.8)
- [CVE-2023-3452](https://insights.sbomify.com/CVE-2023-3452/): Canto <= 3.0.4 - Unauthenticated Remote File Inclusion (critical 9.8)
- [CVE-2022-40305](https://insights.sbomify.com/CVE-2022-40305/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-24063](https://insights.sbomify.com/CVE-2020-24063/): Server-side request forgery in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28978 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Nov 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-28978 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-28978/ (Markdown: https://insights.sbomify.com/CVE-2020-28978/index.md)
```

## Sources

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

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