# CVE-2021-43397: LiquidFiles before 3.6.3 allows remote attackers to elevate their privileges from Admin (or User Admin) to Sysadmin.


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-94g8-mj3r-8gr4

## What is CVE-2021-43397?

CVE-2021-43397 is a high-severity vulnerability in n/a, published on 11 Nov 2021. 

### Official description

LiquidFiles before 3.6.3 allows remote attackers to elevate their privileges from Admin (or User Admin) to Sysadmin.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Liquidfiles Liquidfiles.

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

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

## Is CVE-2021-43397 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-46093](https://insights.sbomify.com/CVE-2025-46093/): Privilege escalation in LiquidFiles (critical 9.9)
- [CVE-2020-29071](https://insights.sbomify.com/CVE-2020-29071/): Cross-site scripting in n/a (critical 9.0)
- [CVE-2025-56132](https://insights.sbomify.com/CVE-2025-56132/): Information disclosure in n/a (high 7.3)
- [CVE-2020-29072](https://insights.sbomify.com/CVE-2020-29072/): Information disclosure in n/a (medium 6.1)
- [CVE-2023-4393](https://insights.sbomify.com/CVE-2023-4393/): HTML and SMTP Injection in LiquidFiles (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43397 is a high-severity vulnerability in n/a, published on 11 Nov 2021. 
Exploitation: There is no known exploitation of CVE-2021-43397 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-2021-43397/ (Markdown: https://insights.sbomify.com/CVE-2021-43397/index.md)
```

## Sources

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

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