# CVE-2015-2747: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via crafted emails or HTTP requests in Websense Triton DLP appliances, requiring user interaction to trigger the policy.

- **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:** 26 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wqm3-6h48-8p64

## What is CVE-2015-2747?

CVE-2015-2747 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Mar 2015. 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 the data loss prevention (DLP) incident Forensics Preview in Websense Triton 7.8.3 and V-Series 7.7 appliances allow remote attackers to inject arbitrary web script or HTML via a crafted (1) email or (2) HTTP request, which triggers a DLP Policy.

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

## Which versions are affected by CVE-2015-2747?

It affects 2 products.


Products: Websense Triton, Websense V-Series Appliances.

## How do I fix CVE-2015-2747?

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

## Is CVE-2015-2747 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2746](https://insights.sbomify.com/CVE-2015-2746/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2747 and fix it if it is affected.

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

## Sources

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

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