CVE-2026-119048

JeeSite AI CMS chat lacks consistent conversation ownership checks

ThinkGem / JeeSite · JeeSite AI CMS chat module

First documented disclosure · Review checkpoint

Summary

Authenticated users may access another user’s cached AI conversation.

Severity and exploitation evidence

Low · 2.3/10 · CVSS 4.0. Severity source.

Exploitation not established: Researcher performed static source review, explicitly without runtime validation or live exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

A missing read check and reversed prefix comparison undermine ownership checks.

Conditions required

A valid account, AI CMS module, and a known or derived victim conversation ID that remains cached.

Potential impact

Reading, deleting or appending to cached conversations; remote code execution and credential access are not established.

Affected versions and configurations

5.11.0 through 5.19.1, per CNA.

Fix and mitigation status

Upstream commit cbc5ba7a37fd93f38c46ef656bd31442fe6f8015; no numbered fixed release verified.

Practical next steps

Apply the upstream ownership-check fix or a supported release containing it; restrict AI CMS chat until deployed.

Operating lesson

Bind conversations to a server-side owner and verify that owner at every read and mutation.

Evidence and limits

Issue, fix and CNA published October 29. VulnCheck scores CVSS4.0 2.3 and CVSS3.1 4.2; the displayed score uses 4.0. The example requests are illustrative, not demonstrated compromise.

Sources