# CVE-2026-97897: Krayin laravel-crm TinyMCE Media Upload Sanitizer.php cross site scripting

> Remote attackers can inject malicious scripts via TinyMCE media uploads in Krayin Laravel CRM, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **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:** 25 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-vqgc-ppr5-jjg9

## What is CVE-2026-97897?

CVE-2026-97897 is a medium-severity cross-site scripting vulnerability in Krayin laravel-crm, published on 25 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A security flaw has been discovered in Krayin laravel-crm up to 2.2.5. This issue affects some unknown processing of the file Sanitizer.php of the component TinyMCE Media Upload. The manipulation results in cross site scripting. The attack may be performed from remote. Upgrading to version 2.2.6 is capable of addressing this issue. The patch is identified as 734aa10ae6c2ffa4c96c8869a89aa66940e4d345. You should upgrade the affected component.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-97897 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-97897 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97897 is a medium-severity cross-site scripting vulnerability in Krayin laravel-crm, published on 25 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-97897 exists.

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

## Sources

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

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