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

> Unspecified vulnerabilities in Epiware, potentially including XSS, allow attackers to execute scripts or perform other actions against users.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pvw4-3rwc-f79f

## What is CVE-2007-1197?

CVE-2007-1197 is a critical cross-site scripting vulnerability in n/a, published on 2 Mar 2007. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Multiple unspecified vulnerabilities in Epiware before 4.7.5 have unknown impact and attack vectors, possibly related to cross-site scripting (XSS) and other unspecified issues.

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

It affects 1 product.


Products: Epiware Epiware.

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

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

## Is CVE-2007-1197 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1197 is a critical cross-site scripting vulnerability in n/a, published on 2 Mar 2007. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-1197 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-2007-1197/ (Markdown: https://insights.sbomify.com/CVE-2007-1197/index.md)
```

## Sources

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

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