LaSuite Doc: Public Documents Enumeration
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-76907
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 14:04 UTC · Revision 1
Source evidence
LaSuite Doc: Public Documents Enumeration
core-osv · Original sourcePublished 24 Sept 2026, 15:44 UTC
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.
osv:CVE-2026-76907
Complete source record
{
"id": "0153a5aacd2362ce033d03c52f321532d5e8390e1e8a41f4f1a6d2fa3b083744",
"url": "https://osv.dev/vulnerability/CVE-2026-76907",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "LaSuite Doc: Public Documents Enumeration",
"summary": "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.",
"evidence": "osv:CVE-2026-76907",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-76907",
"aliases": [
"CVE-2026-76907",
"GHSA-p8v2-wjj3-3j9w"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/suitenumerique/docs",
"type": "GIT",
"events": [
{
"introduced": "0867ccef1ae4d4dc7fe5465879c3a596ffbd1dd8"
},
{
"fixed": "f5e43a092174d4c3b617dc2383e336a00f826101"
},
{
"fixed": "9ef4a15f5e7437c73ad04d2115a15dba3ffb7a76"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "4.8.2"
},
{
"fixed": "5.4.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "9ef4a15f5e7437c73ad04d2115a15dba3ffb7a76"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "f5e43a092174d4c3b617dc2383e336a00f826101"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v5.4.0"
}
]
}
}
],
"versions": [
"v5.3.0-preprod",
"v5.3.0",
"v5.2.1-preprod",
"v5.2.1",
"v5.2.0-preprod",
"v5.2.0",
"v5.1.0",
"v4.8.6",
"v4.8.5-preprod",
"v4.8.5",
"v4.8.4-preprod",
"v4.8.4",
"v4.8.3",
"v4.8.2-preprod",
"v4.8.2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-76907.json"
}
}
],
"modified": "2026-10-28T02:30:36.299353165Z",
"provider": "osv",
"references": [
"https://github.com/suitenumerique/docs/releases/tag/v5.4.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/76xxx/CVE-2026-76907.json",
"https://github.com/suitenumerique/docs/security/advisories/GHSA-p8v2-wjj3-3j9w",
"https://nvd.nist.gov/vuln/detail/CVE-2026-76907",
"https://github.com/suitenumerique/docs/commit/9ef4a15f5e7437c73ad04d2115a15dba3ffb7a76"
],
"provider_metadata": {
"cwe_ids": [
"CWE-200",
"CWE-639"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/76xxx/CVE-2026-76907.json"
}
},
"related_cves": [
{
"value": "CVE-2026-76907",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 503389,
"published_at": "2026-09-24T15:44:45.292+00:00"
}