# CVE-2021-46107: Server-side request forgery in n/a

> An attacker can exploit a Server Side Request Forgery vulnerability in Ligeo Archives to read any documents via the download features.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 17 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wj9r-vmgq-6f4j

## What is CVE-2021-46107?

CVE-2021-46107 is a high-severity server-side request forgery vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ligeo Archives Ligeo Basics as of 02_01-2022 is vulnerable to Server Side Request Forgery (SSRF) which allows an attacker to read any documents via the download features.

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

## Which versions are affected by CVE-2021-46107?

It affects 1 product.


Products: Ligeo-Archives Ligeo Basics.

## How do I fix CVE-2021-46107?

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

## Is CVE-2021-46107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-46107 exists.

Public exploit code:

- Ligeo Archives Ligeo Basics - Server Side Request Forgery (nuclei): http/cves/2021/CVE-2021-46107.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46107 and fix it if it is affected.

What it is: CVE-2021-46107 is a high-severity server-side request forgery vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-46107 exists.

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-2021-46107/ (Markdown: https://insights.sbomify.com/CVE-2021-46107/index.md)
```

## Sources

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

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