# CVE-2009-5103: Cross-site scripting (XSS) vulnerability in ATCOM Netvolution 1.0 ASP allows remote attackers to inject arbitrary web script or HTML via the email variable.


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-65jr-xp2m-mpxq

## What is CVE-2009-5103?

CVE-2009-5103 is a medium-severity vulnerability in n/a, published on 21 Oct 2011. 

### Official description

Cross-site scripting (XSS) vulnerability in ATCOM Netvolution 1.0 ASP allows remote attackers to inject arbitrary web script or HTML via the email variable.

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

## Which versions are affected by CVE-2009-5103?

It affects 1 product.


Products: Atcom Netvolution.

## How do I fix CVE-2009-5103?

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

## Is CVE-2009-5103 being exploited?

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

Public exploit code:

- Netvolution CMS 1.0 - Cross-Site Scripting / SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-2318](https://insights.sbomify.com/CVE-2014-2318/): SQL injection in n/a (high 7.5)
- [CVE-2009-5102](https://insights.sbomify.com/CVE-2009-5102/): SQL injection in n/a (high 7.5)
- [CVE-2010-4967](https://insights.sbomify.com/CVE-2010-4967/): SQL injection in n/a (high 7.5)
- [CVE-2011-3340](https://insights.sbomify.com/CVE-2011-3340/): SQL injection in n/a (high 7.5)
- [CVE-2010-4966](https://insights.sbomify.com/CVE-2010-4966/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5103 and fix it if it is affected.

What it is: CVE-2009-5103 is a medium-severity vulnerability in n/a, published on 21 Oct 2011. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-5103 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-2009-5103/ (Markdown: https://insights.sbomify.com/CVE-2009-5103/index.md)
```

## Sources

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

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