# CVE-2026-107798: Jivejdon through commit ee67a65e Stored XSS via Markdown Links in TextStyle Rendering Filter

> Authenticated attackers can inject JavaScript via Markdown links in Jivejdon, leading to script execution when other users interact with the content.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA: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:** 8 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-x3wr-65j4-jv4v

## What is CVE-2026-107798?

CVE-2026-107798 is a medium-severity cross-site scripting vulnerability in banq jivejdon, published on 8 Oct 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

jivejdon from commit 595d8d22 through commit ee67a65e contains a stored cross-site scripting vulnerability in the default-enabled TextStyle filter that inserts unvalidated URLs into anchor href attributes. Authenticated attackers can post messages with javascript: links or quote-breaking URLs to execute JavaScript when other users click or hover over rendered links.

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

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


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

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

## Is CVE-2026-107798 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107798 is a medium-severity cross-site scripting vulnerability in banq jivejdon, published on 8 Oct 2026. 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-2026-107798 in the wild and no public exploit code.

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

## Sources

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

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