# CVE-2013-6314: Cross-site scripting in n/a

> Authenticated attackers can inject malicious scripts into IBM InfoSphere Enterprise Records, potentially compromising user sessions or data.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h9pw-g98h-m66f

## What is CVE-2013-6314?

CVE-2013-6314 is a low-severity cross-site scripting vulnerability in n/a, published on 6 Mar 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in IBM InfoSphere Enterprise Records 4.5.1 before 4.5.1.7-IER-IF001 and Enterprise Records 5.1.1 before 5.1.1.1-IER-IF003 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors.

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

## Which versions are affected by CVE-2013-6314?

It affects 2 products.


Products: Ibm Enterprise Records, Ibm Infosphere Enterprise Records.

## How do I fix CVE-2013-6314?

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

## Is CVE-2013-6314 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6315](https://insights.sbomify.com/CVE-2013-6315/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6314 and fix it if it is affected.

What it is: CVE-2013-6314 is a low-severity cross-site scripting vulnerability in n/a, published on 6 Mar 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-6314 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-2013-6314/ (Markdown: https://insights.sbomify.com/CVE-2013-6314/index.md)
```

## Sources

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

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