# CVE-2006-1702: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in SPIP CMS via a URL parameter in the login 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:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1702, GHSA-36wc-4rp7-pvp7

## What is CVE-2006-1702?

CVE-2006-1702 is a high-severity code injection vulnerability in Spip Spip, published on 11 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in spip_login.php3 in SPIP 1.8.3 allows remote attackers to execute arbitrary PHP code via a URL in the url parameter.

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

It affects 1 product.


Products: Spip Spip.

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

Upgrade to a fixed version.

## Is CVE-2006-1702 being exploited?

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

Public exploit code:

- SPIP 1.8.3 - 'Spip_login.php' Remote File Inclusion (exploitdb)

## Other vulnerabilities in Spip Spip

- [CVE-2012-4331](https://insights.sbomify.com/CVE-2012-4331/): Other in n/a (critical 10.0)
- [CVE-2008-5812](https://insights.sbomify.com/CVE-2008-5812/): Other in n/a (critical 10.0)
- [CVE-2024-8517](https://insights.sbomify.com/CVE-2024-8517/): SPIP Bigup Multipart File Upload OS Command Injection (critical 9.8)
- [CVE-2023-24258](https://insights.sbomify.com/CVE-2023-24258/): SQL injection in n/a (critical 9.8)
- [CVE-2017-9736](https://insights.sbomify.com/CVE-2017-9736/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1702 is a high-severity code injection vulnerability in Spip Spip, published on 11 Apr 2006. 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-2006-1702 exists.

Affected product: Spip Spip. 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-1702/ (Markdown: https://insights.sbomify.com/CVE-2006-1702/index.md)
```

## Sources

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

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