# CVE-2006-1703: PHP remote file inclusion vulnerability in lire.php in Sire 2.0 nws allows remote attackers to execute arbitrary PHP code via a URL in the rub parameter.


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f5w9-33q4-c5j7

## What is CVE-2006-1703?

CVE-2006-1703 is a high-severity vulnerability in n/a, published on 11 Apr 2006. 

### Official description

PHP remote file inclusion vulnerability in lire.php in Sire 2.0 nws allows remote attackers to execute arbitrary PHP code via a URL in the rub parameter.

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

It affects 1 product.


Products: Hubert Plisson Sire.

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

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

## Is CVE-2006-1703 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1704](https://insights.sbomify.com/CVE-2006-1704/): File upload in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1703 is a high-severity vulnerability in n/a, published on 11 Apr 2006. 
Exploitation: There is no known exploitation of CVE-2006-1703 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-1703/ (Markdown: https://insights.sbomify.com/CVE-2006-1703/index.md)
```

## Sources

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

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