# CVE-2021-47901: dirsearch 0.4.1 - CSV Injection

> Attackers can inject malicious Excel formulas into CSV reports generated by Dirsearch, potentially leading to code execution when the report is opened.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-3pqc-wf77-h389

## What is CVE-2021-47901?

CVE-2021-47901 is a medium-severity vulnerability in maurosoria dirsearch, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Dirsearch 0.4.1 contains a CSV injection vulnerability when using the --csv-report flag that allows attackers to inject formulas through redirected endpoints. Attackers can craft malicious server redirects with comma-separated paths containing Excel formulas to manipulate the generated CSV report.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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


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

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

## Is CVE-2021-47901 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-47901 is a medium-severity vulnerability in maurosoria dirsearch, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47901 exists.

Affected product: maurosoria dirsearch. 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-47901/ (Markdown: https://insights.sbomify.com/CVE-2021-47901/index.md)
```

## Sources

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

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