# CVE-2007-0364: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in INDEXU, potentially leading to session hijacking or malicious actions.

- **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:** 19 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xgcg-pv4v-c96w

## What is CVE-2007-0364?

CVE-2007-0364 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Jan 2007. 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

Multiple cross-site scripting (XSS) vulnerabilities in nicecoder.com INDEXU 5.3 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) error_msg parameter to (a) suggest_category.php; the (2) u parameter to (b) user_detail.php; the (3) friend_name, (4) friend_email, (5) error_msg, (6) my_name, (7) my_email, and (8) id parameters to (c) tell_friend.php; the (9) error_msg, (10) email, (11) name, and (12) subject parameters to (d) sendmail.php; the (13) email, (14) error_msg, and (15) username parameters to (e) send_pwd.php; the (16) keyword parameter to (f) search.php; the (17) error_msg, (18) username, (19) password, (20) password2, and (21) email parameters to (g) register.php; the (22) url, (23) contact_name, and (24) email parameters to (h) power_search.php; the (25) path and (26) total parameters to (i) new.php; the (27) query parameter to (j) modify.php; the (28) error_msg parameter to (k) login.php; the (29) error_msg and (30) email parameters to (l) mailing_list.php; the (31) gateway parameter to (m) upgrade.php; and another unspecified vector.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2007-0364?

It affects 1 product.


Products: Nicecoder Indexu.

## How do I fix CVE-2007-0364?

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

## Is CVE-2007-0364 being exploited?

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

Public exploit code:

- Indexu 5.0/5.3 - 'upgrade.php?gateway' Cross-Site Scripting (exploitdb)
- Indexu 5.0/5.3 - 'suggest_category.php?Error_msg' Cross-Site Scripting (exploitdb)
- Indexu 5.0/5.3 - 'user_detail.php?u' Cross-Site Scripting (exploitdb)
- Indexu 5.0/5.3 - 'tell_friend.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- Indexu 5.0/5.3 - 'Sendmail.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- Indexu 5.0/5.3 - 'send_pwd.php' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-7017](https://insights.sbomify.com/CVE-2006-7017/): File upload in n/a (high 7.5)
- [CVE-2006-1767](https://insights.sbomify.com/CVE-2006-1767/): Code injection in n/a (high 7.5)
- [CVE-2006-0688](https://insights.sbomify.com/CVE-2006-0688/): Code injection in n/a (high 7.5)
- [CVE-2007-0349](https://insights.sbomify.com/CVE-2007-0349/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0364 and fix it if it is affected.

What it is: CVE-2007-0364 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Jan 2007. 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-2007-0364 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-2007-0364/ (Markdown: https://insights.sbomify.com/CVE-2007-0364/index.md)
```

## Sources

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

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