DocsGPT through 0.20.0 OAuth Token Disclosure via Wildcard postMessage
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| arc53 | DocsGPT | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Arc53 | Docsgpt |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.208% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | DocsGPT through 0.20.0 posts OAuth connector session tokens to a wildcard target origin in the callback-status endpoint without validating sender origin. Attackers can obtain session tokens and provider account emails by acting as window.opener during OAuth authorization, then use tokens to disconnect victims' cloud storage connectors. | |
| Title | DocsGPT through 0.20.0 OAuth Token Disclosure via Wildcard postMessage | |
| First Time appeared |
Arc53
Arc53 docsgpt |
|
| Weaknesses | CWE-346 | |
| CPEs | cpe:2.3:a:arc53:docsgpt:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Arc53
Arc53 docsgpt |
|
| References |
|
|
| Metrics |
cvssV3_1
|