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

> Hard-coded admin password hashes in source files allow attackers to crack credentials and gain administrative access to the blog.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j7hx-82r8-x847

## What is CVE-2020-25987?

CVE-2020-25987 is a high-severity vulnerability in n/a, published on 6 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MonoCMS Blog 1.0 stores hard-coded admin hashes in the log.xml file in the source files for MonoCMS Blog. Hash type is bcrypt and hashcat mode 3200 can be used to crack the hash.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Monocms Monocms.

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

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

## Is CVE-2020-25987 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25985](https://insights.sbomify.com/CVE-2020-25985/): Path traversal in n/a (high 8.1)
- [CVE-2020-28672](https://insights.sbomify.com/CVE-2020-28672/): File upload in n/a (high 7.2)
- [CVE-2020-25986](https://insights.sbomify.com/CVE-2020-25986/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2024-10927](https://insights.sbomify.com/CVE-2024-10927/): MonoCMS Account Information Page account.php cross site scripting (medium 5.3)
- [CVE-2024-10928](https://insights.sbomify.com/CVE-2024-10928/): MonoCMS Posts Page opensaved.php cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25987 is a high-severity vulnerability in n/a, published on 6 Oct 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-25987 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-25987/ (Markdown: https://insights.sbomify.com/CVE-2020-25987/index.md)
```

## Sources

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

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