# CVE-2018-0604: Code injection in Pixelpost

> Remote attackers can execute arbitrary code on Pixelpost blog installations, posing a critical risk to site integrity and data.

- **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:** 26 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gpwc-59gx-c48m

## What is CVE-2018-0604?

CVE-2018-0604 is a high-severity code injection vulnerability in Pixelpost.org Pixelpost, published on 26 Jun 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Pixelpost v1.7.3 and earlier allows remote code execution via unspecified vectors.

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

It affects 1 product.


Products: Pixelpost Pixelpost.

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

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

## Is CVE-2018-0604 being exploited?

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

## Other vulnerabilities in Pixelpost.org Pixelpost

- [CVE-2009-4899](https://insights.sbomify.com/CVE-2009-4899/): pixelpost 1.7.1 has SQL injection (critical 9.8)
- [CVE-2010-3305](https://insights.sbomify.com/CVE-2010-3305/): Cross-site request forgery in pixelpost (high 8.8)
- [CVE-2006-1104](https://insights.sbomify.com/CVE-2006-1104/): SQL injection in n/a (high 7.5)
- [CVE-2018-0606](https://insights.sbomify.com/CVE-2018-0606/): SQL injection in Pixelpost (high 7.2)
- [CVE-2008-3365](https://insights.sbomify.com/CVE-2008-3365/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-0604 is a high-severity code injection vulnerability in Pixelpost.org Pixelpost, published on 26 Jun 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0604 in the wild and no public exploit code.

Affected product: Pixelpost.org Pixelpost. 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-0604/ (Markdown: https://insights.sbomify.com/CVE-2018-0604/index.md)
```

## Sources

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

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