# CVE-2005-2603: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via parameters in My Image Gallery, requiring user interaction to execute.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ppqg-jc7r-6vmq

## What is CVE-2005-2603?

CVE-2005-2603 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Aug 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in index.php for My Image Gallery (Mig ) 1.4.1 allows remote attackers to inject arbitrary web script or HTML via the (1) currDir or (2) image parameters.

## Which versions are affected by CVE-2005-2603?

It affects 1 product.


Products: My Image Gallery My Image Gallery.

## How do I fix CVE-2005-2603?

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

## Is CVE-2005-2603 being exploited?

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

Public exploit code:

- My Image Gallery 1.4.1 - 'index.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2604](https://insights.sbomify.com/CVE-2005-2604/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2603 and fix it if it is affected.

What it is: CVE-2005-2603 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Aug 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2603 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-2005-2603/ (Markdown: https://insights.sbomify.com/CVE-2005-2603/index.md)
```

## Sources

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

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