# CVE-2026-107831: Jivejdon through 5.0 CSRF via GET-based Account and Thread Actions

> Remote attackers can trick authenticated users into deleting messages or renaming threads via crafted GET links in Jivejdon.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-4fm4-wvj2-74v3

## What is CVE-2026-107831?

CVE-2026-107831 is a medium-severity vulnerability in banq jivejdon, published on 8 Oct 2026. 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

Jivejdon through 5.0 contains a cross-site request forgery vulnerability that allows remote attackers to perform state-changing actions by abusing GET endpoints lacking anti-CSRF tokens. Attackers can lure authenticated users to crafted links targeting /account/protected/delAll, /account/protected/sub/delSub, or /message/updateAction to delete private messages and subscriptions or rename threads.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-107831 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107831 is a medium-severity vulnerability in banq jivejdon, published on 8 Oct 2026. 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-2026-107831 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-107831/ (Markdown: https://insights.sbomify.com/CVE-2026-107831/index.md)
```

## Sources

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

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