# CVE-2018-18753: Server-side request forgery in n/a

> Remote attackers can execute shell commands and perform SSRF attacks via base64-encoded serialized data in Typecho.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 28 Oct 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cw4f-c442-gqwh

## What is CVE-2018-18753?

CVE-2018-18753 is a critical server-side request forgery vulnerability in n/a, published on 28 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Typecho V1.1 allows remote attackers to send shell commands via base64-encoded serialized data, as demonstrated by SSRF.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Typecho Typecho.

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

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

## Is CVE-2018-18753 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-24114](https://insights.sbomify.com/CVE-2023-24114/): Code injection in n/a (critical 9.8)
- [CVE-2023-36299](https://insights.sbomify.com/CVE-2023-36299/): File upload in n/a (high 8.8)
- [CVE-2024-35540](https://insights.sbomify.com/CVE-2024-35540/): Cross-site scripting in n/a (high 7.6)
- [CVE-2023-49967](https://insights.sbomify.com/CVE-2023-49967/): Denial of service in n/a (high 7.5)
- [CVE-2024-35539](https://insights.sbomify.com/CVE-2024-35539/): Race condition in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18753 is a critical server-side request forgery vulnerability in n/a, published on 28 Oct 2018. 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-2018-18753 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-18753/ (Markdown: https://insights.sbomify.com/CVE-2018-18753/index.md)
```

## Sources

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

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