# CVE-2005-2691: Other in n/a

> Remote attackers can overwrite arbitrary variables via HTTP POST requests in RunCMS, potentially leading to arbitrary code execution.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vhg4-4fwp-2prc

## What is CVE-2005-2691?

CVE-2005-2691 is a high-severity vulnerability in n/a, published on 24 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

includes/common.php in RunCMS 1.2 and earlier calls the extract function with EXTR_OVERWRITE on HTTP POST variables, which allows remote attackers to overwrite arbitrary variables, possibly allowing execution of arbitrary code.

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

It affects 1 product.


Products: Runcms Runcms.

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

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

## Is CVE-2005-2691 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5535](https://insights.sbomify.com/CVE-2007-5535/): Unspecified vulnerability in newbb_plus in RunCms 1.5.2 has unknown impact and attack vectors. (critical 10.0)
- [CVE-2007-2539](https://insights.sbomify.com/CVE-2007-2539/): Information disclosure in n/a (high 7.8)
- [CVE-2006-1793](https://insights.sbomify.com/CVE-2006-1793/): Path traversal in n/a (high 7.6)
- [CVE-2008-0224](https://insights.sbomify.com/CVE-2008-0224/): SQL injection in n/a (high 7.5)
- [CVE-2007-6544](https://insights.sbomify.com/CVE-2007-6544/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2691 is a high-severity vulnerability in n/a, published on 24 Aug 2005. 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-2005-2691 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-2005-2691/ (Markdown: https://insights.sbomify.com/CVE-2005-2691/index.md)
```

## Sources

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

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