Documize Community - Attachment Download Authorization Bypass via Non-Validated secure Token
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| documize | community | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Documize | Community |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.394% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/documize/community |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Documize Community's attachment download route (domain/attachment/endpoint.go, Download function, registered via AddPublic with no auth middleware) accepts a `secure` query parameter and grants access whenever the parameter is simply non-empty (len(secureToken) > 0), without comparing it to any server-stored value. Any non-empty string, such as ?secure=x, bypasses authentication entirely and allows downloading any organization's attachments. Sibling handlers in the same file (togglePublish, delete) correctly enforce session-based authorization, confirming this is an inconsistency rather than intended design. | Documize Community's attachment download route (domain/attachment/endpoint.go, Download function, registered via AddPublic with no auth middleware) accepts a query parameter and grants access whenever the parameter is simply non-empty (len(secureToken) > 0), without comparing it to any server-stored value. |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Documize Community: Attachment Download Authorization Bypass via Non-Validated secure Token | Documize Community - Attachment Download Authorization Bypass via Non-Validated secure Token |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Documize
Documize community |
|
| Vendors & Products |
Documize
Documize community |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Documize Community's attachment download route (domain/attachment/endpoint.go, Download function, registered via AddPublic with no auth middleware) accepts a `secure` query parameter and grants access whenever the parameter is simply non-empty (len(secureToken) > 0), without comparing it to any server-stored value. Any non-empty string, such as ?secure=x, bypasses authentication entirely and allows downloading any organization's attachments. Sibling handlers in the same file (togglePublish, delete) correctly enforce session-based authorization, confirming this is an inconsistency rather than intended design. | |
| Title | Documize Community: Attachment Download Authorization Bypass via Non-Validated secure Token | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|