# CVE-2003-1179: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in Advanced Poll via remote file inclusion in multiple scripts.

- **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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7h7c-qh2g-25rw

## What is CVE-2003-1179?

CVE-2003-1179 is a high-severity code injection vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP remote file inclusion vulnerabilities in Advanced Poll 2.0.2 allow remote attackers to execute arbitrary PHP code via the include_path parameter in (1) booth.php, (2) png.php, (3) poll_ssi.php, or (4) popup.php, the (5) base_path parameter to common.inc.php.

## Which versions are affected by CVE-2003-1179?

It affects 1 product.


Products: Advanced Poll Advanced Poll.

## How do I fix CVE-2003-1179?

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

## Is CVE-2003-1179 being exploited?

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

Public exploit code:

- Advanced Poll 2.0.2 - 'common.inc.php' Remote File Inclusion (exploitdb)

## 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-1180](https://insights.sbomify.com/CVE-2003-1180/): Path traversal in n/a (high 7.5)
- [CVE-2001-1423](https://insights.sbomify.com/CVE-2001-1423/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1179 and fix it if it is affected.

What it is: CVE-2003-1179 is a high-severity code injection vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1179 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-2003-1179/ (Markdown: https://insights.sbomify.com/CVE-2003-1179/index.md)
```

## Sources

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

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