# CVE-2020-12627: Hardcoded credentials in n/a

> Attackers can bypass authentication in Calibre-Web due to a hardcoded secret key, gaining unauthorized access to the application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 4 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9q6c-4f46-hgf2

## What is CVE-2020-12627?

CVE-2020-12627 is a critical vulnerability in n/a, published on 4 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Calibre-Web 0.6.6 allows authentication bypass because of the 'A0Zr98j/3yX R~XHH!jmN]LWX/,?RT' hardcoded secret key.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Janeczku Calibre-Web.

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

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

## Is CVE-2020-12627 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30765](https://insights.sbomify.com/CVE-2022-30765/): SQL injection in calibreweb (critical 9.8)
- [CVE-2022-0990](https://insights.sbomify.com/CVE-2022-0990/): Server-Side Request Forgery (SSRF) in janeczku/calibre-web (critical 9.3)
- [CVE-2022-0767](https://insights.sbomify.com/CVE-2022-0767/): Server-Side Request Forgery (SSRF) in janeczku/calibre-web (critical 9.1)
- [CVE-2022-0939](https://insights.sbomify.com/CVE-2022-0939/): Server-Side Request Forgery (SSRF) in janeczku/calibre-web (critical 9.0)
- [CVE-2021-25965](https://insights.sbomify.com/CVE-2021-25965/): Calibre-web - Admin Account Takeover via Cross-Site Request Forgery (CSRF) (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12627 is a critical vulnerability in n/a, published on 4 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12627 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-12627/ (Markdown: https://insights.sbomify.com/CVE-2020-12627/index.md)
```

## Sources

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

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