# CVE-2018-11209: Weak cryptography in n/a

> Z-BlogPHP uses MD5 for password verification, allowing attackers to bypass access restrictions via dictionary or rainbow-table attacks.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hvj4-mm2p-82f7

## What is CVE-2018-11209?

CVE-2018-11209 is a high-severity vulnerability in n/a, published on 16 May 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Z-BlogPHP 2.0.0. zb_system/cmd.php?act=verify relies on MD5 for the password parameter, which might make it easier for attackers to bypass intended access restrictions via a dictionary or rainbow-table attack. NOTE: the vendor declined to accept this as a valid issue

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2018-11209?

It affects 1 product.


Products: Zblogcn Z-Blogphp.

## How do I fix CVE-2018-11209?

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

## Is CVE-2018-11209 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-55529](https://insights.sbomify.com/CVE-2024-55529/): Code injection in n/a (critical 9.8)
- [CVE-2022-40357](https://insights.sbomify.com/CVE-2022-40357/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-29177](https://insights.sbomify.com/CVE-2020-29177/): Path traversal in n/a (critical 9.1)
- [CVE-2018-19463](https://insights.sbomify.com/CVE-2018-19463/): File upload in n/a (high 8.8)
- [CVE-2018-18842](https://insights.sbomify.com/CVE-2018-18842/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11209 and fix it if it is affected.

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

## Sources

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

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