# CVE-2009-4900: pixelpost 1.7.1 has XSS


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2019
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rqr2-vwcj-g935

## What is CVE-2009-4900?

CVE-2009-4900 is a medium-severity vulnerability in n/a, published on 28 Oct 2019. 

### Official description

pixelpost 1.7.1 has XSS

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2009-4900?

It affects 1 product.


Products: Pixelpost Pixelpost.

## How do I fix CVE-2009-4900?

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

## Is CVE-2009-4900 being exploited?

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

## Other vulnerabilities in n/a

- [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-0604](https://insights.sbomify.com/CVE-2018-0604/): Code injection in Pixelpost (high 7.2)
- [CVE-2018-0606](https://insights.sbomify.com/CVE-2018-0606/): SQL injection in Pixelpost (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4900 and fix it if it is affected.

What it is: CVE-2009-4900 is a medium-severity vulnerability in n/a, published on 28 Oct 2019. 
Exploitation: There is no known exploitation of CVE-2009-4900 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-2009-4900/ (Markdown: https://insights.sbomify.com/CVE-2009-4900/index.md)
```

## Sources

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

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