# CVE-2006-5931: File upload in n/a

> Remote attackers can execute arbitrary PHP code via URL injection in the DIR parameter when register_globals is enabled.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 16 Nov 2006
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-97h5-f2m3-8jfr

## What is CVE-2006-5931?

CVE-2006-5931 is a medium-severity vulnerability in n/a, published on 16 Nov 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 Aigaion Web based bibliography management system 1.2.1, when register_globals is enabled, allow remote attackers to execute arbitrary PHP code via a URL in the DIR parameter to certain PHP scripts in (1) lib/actions/, (2) lib/displays/, (3) lib/editforms/, (4) lib/functions/, (5) scheme/, and (6) the root directory.  NOTE: the provenance of this information is unknown; details are obtained from third party sources.

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

It affects 1 product.


Products: Aigaion Aigaion.

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

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

## Is CVE-2006-5931 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4503](https://insights.sbomify.com/CVE-2010-4503/): SQL injection in n/a (high 7.5)
- [CVE-2007-3683](https://insights.sbomify.com/CVE-2007-3683/): SQL injection in n/a (high 7.5)
- [CVE-2006-5930](https://insights.sbomify.com/CVE-2006-5930/): Code injection in n/a (high 7.5)
- [CVE-2007-3078](https://insights.sbomify.com/CVE-2007-3078/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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