# CVE-2012-5175: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into KENT-WEB ACCESS REPORT via access-log data, 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:** 6 Dec 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9g9m-7c93-hpvq

## What is CVE-2012-5175?

CVE-2012-5175 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Dec 2012. 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 KENT-WEB ACCESS REPORT 4.2 and earlier allows remote attackers to inject arbitrary web script or HTML via vectors related to access-log data.

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

## Which versions are affected by CVE-2012-5175?

It affects 1 product.


Products: Kent-Web Access Report.

## How do I fix CVE-2012-5175?

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

## Is CVE-2012-5175 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5176](https://insights.sbomify.com/CVE-2012-5176/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5175 and fix it if it is affected.

What it is: CVE-2012-5175 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Dec 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-5175 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-2012-5175/ (Markdown: https://insights.sbomify.com/CVE-2012-5175/index.md)
```

## Sources

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

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