# CVE-2005-2564: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via the csscontent parameter in Gravity Board X's editcss.php script.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f9w5-x8gf-63m5

## What is CVE-2005-2564?

CVE-2005-2564 is a high-severity code injection vulnerability in n/a, published on 16 Aug 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Direct static code injection vulnerability in editcss.php in Gravity Board X (GBX) 1.1 allows remote attackers to execute arbitrary PHP code, HTML, and script via the csscontent parameter, which is directly inserted into the gbxfinal.css file.

## Which versions are affected by CVE-2005-2564?

It affects 1 product.


Products: Gravity Board X Development Team Gravity Board X.

## How do I fix CVE-2005-2564?

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

## Is CVE-2005-2564 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2564 exists.

Public exploit code:

- Gravity Board X 1.1 - 'csscontent' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2562](https://insights.sbomify.com/CVE-2005-2562/): SQL injection in n/a (high 7.5)
- [CVE-2005-2565](https://insights.sbomify.com/CVE-2005-2565/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-2563](https://insights.sbomify.com/CVE-2005-2563/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2564 and fix it if it is affected.

What it is: CVE-2005-2564 is a high-severity code injection vulnerability in n/a, published on 16 Aug 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2564 exists.

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-2005-2564/ (Markdown: https://insights.sbomify.com/CVE-2005-2564/index.md)
```

## Sources

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

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