# CVE-2020-27997: Cross-site request forgery in n/a

> Attackers can exploit missing CSRF protection to create admin accounts and escalate privileges in SmartStoreNET.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Feb 2021
- **Updated:** 4 Aug 2024

## What is CVE-2020-27997?

CVE-2020-27997 is a high-severity vulnerability in n/a, published on 19 Feb 2021. 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

An issue was discovered in SmartStoreNET before 4.1.0. Lack of Cross Site Request Forgery (CSRF) protection may lead to elevation of privileges (e.g., /admin/customer/create to create an admin account).

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Smartstore Smartstorenet.

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

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

## Is CVE-2020-27997 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36364](https://insights.sbomify.com/CVE-2020-36364/): Path traversal in n/a (critical 9.1)
- [CVE-2020-27996](https://insights.sbomify.com/CVE-2020-27996/): Other in n/a (high 8.8)
- [CVE-2020-36365](https://insights.sbomify.com/CVE-2020-36365/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27997 is a high-severity vulnerability in n/a, published on 19 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-27997 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-27997/ (Markdown: https://insights.sbomify.com/CVE-2020-27997/index.md)
```

## Sources

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

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