CVE-2026-111169: La Suite Docs through 6.0.1 Authorization Bypass via Comment Thread Creation

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

La Suite Docs through 6.0.1 contains an authorization bypass vulnerability that allows authenticated users to write comments into threads of documents they cannot access. Attackers who know a thread UUID can route a POST comment request through their own document’s resource_id, inserting comments into another document’s thread without access.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-15).

Weakness: Authorization Bypass Through User-Controlled Key

How it can be exploited

Exploitable over the network with high attack complexity only when specific conditions are present needing low privileges and no user interaction. Impact: confidentiality none, integrity low, availability none. CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS
0.003
low predicted chance of attack
VEDAS
0.987
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
suitenumerique docsfrom 4.0.0 up to and including 6.0.1Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-111169 La Suite Docs - Broken Access Control Comment Injection into Foreign Thread. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-111169 La Suite Docs - Broken Access Control Comment Injection into Foreign Thread"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/v1.0/documents/"; nocase; fast_pattern; content:"/threads/"; nocase; distance:0; content:"/comments/"; nocase; distance:0; classtype:web-application-attack; reference:cve,CVE-2026-111169; reference:url,https://www.exploit.observer/?keyword=CVE-2026-111169&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=lasuite-docs&match=exact; metadata:signature_type network_only; sid:1083602; rev:1;)

CVE-2026-111169.rules on GitHub

References

Vendor advisories and patches

Technical analysis and advisories

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust