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

> Remote attackers can execute arbitrary PHP code via URL injection in the PROJECT_ROOT parameter of the Open Meetings Filing Application.

- **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:** 26 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-36qp-p5p2-rm5x

## What is CVE-2006-5517?

CVE-2006-5517 is a high-severity code injection vulnerability in n/a, published on 26 Oct 2006. 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 Rhode Island Open Meetings Filing Application (OMFA) allow remote attackers to execute arbitrary PHP code via a URL in the PROJECT_ROOT parameter to (1) editmeetings/session.php, (2) email/session.php, (3) entityproperties/session.php, or (4) inc/mail.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Rhode Island Secretary of State Open Meetings Filing System.

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

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

## Is CVE-2006-5517 being exploited?

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

Public exploit code:

- Open Meetings Filing Application - Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5517 is a high-severity code injection vulnerability in n/a, published on 26 Oct 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-5517 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-2006-5517/ (Markdown: https://insights.sbomify.com/CVE-2006-5517/index.md)
```

## Sources

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

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