# CVE-2020-19670: Auth bypass in n/a

> Attackers can bypass authentication to reset administrator passwords, gaining full control over the Niushop B2B2C platform.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-95gm-vqqp-xfhw

## What is CVE-2020-19670?

CVE-2020-19670 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Niushop B2B2C Multi-Business Basic Edition V1.11, authentication can be bypassed, causing administrators to reset any passwords.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Niushop Niushop.

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

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

## Is CVE-2020-19670 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-19672](https://insights.sbomify.com/CVE-2020-19672/): File upload in n/a (critical 9.8)
- [CVE-2019-16311](https://insights.sbomify.com/CVE-2019-16311/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-16310](https://insights.sbomify.com/CVE-2019-16310/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-19670 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-19670 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-19670/ (Markdown: https://insights.sbomify.com/CVE-2020-19670/index.md)
```

## Sources

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

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