# CVE-2006-2131: Security feature bypass in n/a

> Remote attackers can spoof IP addresses via X-Forwarded-For headers to bypass voting restrictions in Advanced Poll.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hjr6-c9j9-3f8g

## What is CVE-2006-2131?

CVE-2006-2131 is a medium-severity vulnerability in n/a, published on 1 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

include/class_poll.php in Advanced Poll 2.0.4 uses the HTTP_X_FORWARDED_FOR (X-Forwarded-For HTTP header) to identify the IP address of a client, which makes it easier for remote attackers to spoof the source IP and bypass voting restrictions.

## Which versions are affected by CVE-2006-2131?

It affects 1 product.


Products: Advanced Poll Advanced Poll.

## How do I fix CVE-2006-2131?

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

## Is CVE-2006-2131 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0845](https://insights.sbomify.com/CVE-2007-0845/): Auth bypass in n/a (high 7.5)
- [CVE-2006-1616](https://insights.sbomify.com/CVE-2006-1616/): SQL injection in n/a (high 7.5)
- [CVE-2003-1178](https://insights.sbomify.com/CVE-2003-1178/): Code injection in n/a (high 7.5)
- [CVE-2003-1179](https://insights.sbomify.com/CVE-2003-1179/): Code injection in n/a (high 7.5)
- [CVE-2003-1180](https://insights.sbomify.com/CVE-2003-1180/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2131 and fix it if it is affected.

What it is: CVE-2006-2131 is a medium-severity vulnerability in n/a, published on 1 May 2006. 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-2006-2131 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-2006-2131/ (Markdown: https://insights.sbomify.com/CVE-2006-2131/index.md)
```

## Sources

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

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