CVE-2026-76907: LaSuite Doc: Public Documents Enumeration
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-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
LaSuite Doc is a collaborative note taking, wiki and documentation platform. From 4.8.2 until 5.4.0, GET /api/v1.0/documents/search/ accepts sequential seven-digit document paths to scope descendant searches without requiring the caller to possess the public document UUID. An unauthenticated caller can submit an empty search query and iterate predictable path values to enumerate public document subtrees, obtaining document identifiers, titles, creator data, timestamps, and tree metadata. Each disclosed identifier can then be used through normal public-document endpoints to retrieve the document content, and differing 403 Forbidden and 404 Not Found responses reveal whether a guessed path exists. Authenticated users can similarly discover documents with authenticated link reach, while restricted documents remain protected. This issue is fixed in version 5.4.0.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-09-24).
Weakness: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor; CWE-639: Authorization Bypass Through User-Controlled Key
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. 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 5 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
| Product | Affected | Not affected |
|---|---|---|
| Suitenumerique docs | version >= 4.8.2, < 5.4.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-76907 LaSuite Docs - Unauthenticated Document Path Enumeration. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-76907 LaSuite Docs - Unauthenticated Document Path Enumeration"; flow:established,to_server; http.uri; content:"/api/v1.0/documents/search/"; nocase; fast_pattern; content:"path="; nocase; distance:0; pcre:"/[?&]path=\d{7}(?:[^0-9]|$)/"; classtype:web-application-attack; reference:cve,CVE-2026-76907; reference:url,https://www.exploit.observer/?keyword=CVE-2026-76907&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=lasuite&match=exact; sid:1086003; rev:1;)
CVE-2026-76907.rules on GitHub
References
Other references
- https://github.com/suitenumerique/docs/security/advisories/GHSA-p8v2-wjj3-3j9w (x_refsource_CONFIRM)
- https://github.com/suitenumerique/docs/commit/9ef4a15f5e7437c73ad04d2115a15dba3ffb7a76 (x_refsource_MISC)
- https://github.com/suitenumerique/docs/releases/tag/v5.4.0 (x_refsource_MISC)
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