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

> Remote attackers can inject malicious scripts via the SCRIPT_NAME parameter, enabling cross-site scripting attacks against TCExam users.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x29q-pqw3-mf49

## What is CVE-2007-2431?

CVE-2007-2431 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 May 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

Dynamic variable evaluation vulnerability in shared/config/tce_config.php in TCExam 4.0.011 and earlier allows remote attackers to conduct cross-site scripting (XSS) and possibly other attacks by modifying critical variables such as $_SERVER, as demonstrated by injecting web script via the _SERVER[SCRIPT_NAME] parameter.

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

It affects 1 product.


Products: Tecnick.com Tcexam.

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

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

## Is CVE-2007-2431 being exploited?

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

Public exploit code:

- TCExam 4.0.011 - 'SessionUserLang' Shell Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2430](https://insights.sbomify.com/CVE-2007-2430/): Path traversal in n/a (high 7.8)
- [CVE-2007-6288](https://insights.sbomify.com/CVE-2007-6288/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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