# CVE-2026-115513: OpenCATS before 0.12.0 Stored XSS via MRU Navigation Panel


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-7q62-4fwp-9cr6

## What is CVE-2026-115513?

CVE-2026-115513 is a medium-severity vulnerability in OpenCATS, published on 22 Oct 2026. 

### Official description

OpenCATS before 0.12.0 contains a stored cross-site scripting vulnerability that allows a low-privileged authenticated user to inject HTML/JavaScript payloads by setting a Candidate, Company, Contact, Job Order, or List name/title field, which is stored unsanitized and later rendered unescaped in the 'Recent' (MRU) navigation panel displayed on nearly every page via lib/MRU.php's getFormatted() function. Attackers can exploit this by crafting a malicious record name that executes arbitrary JavaScript in the session of any other user, including Site Administrators, who views the record, enabling session/cookie theft and privilege escalation to full administrative control.

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

## Which versions are affected by CVE-2026-115513?


## How do I fix CVE-2026-115513?

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

## Is CVE-2026-115513 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115513 and fix it if it is affected.

What it is: CVE-2026-115513 is a medium-severity vulnerability in OpenCATS, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115513 in the wild and no public exploit code.

Affected product: OpenCATS. 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-2026-115513/ (Markdown: https://insights.sbomify.com/CVE-2026-115513/index.md)
```

## Sources

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

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