JWT Exposure via GET Request in Edito CMS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Edito | Edito CMS | affected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Edito CMS sends JWT token via GET requests. This allows a local attacker with access to browser history to obtain valid JWT token and perform action on behalf of the victim. The token is valid for only short period of time; after that time, it expires and can no longer be used. The vendor assessed the likelihood of exploitation as very low and determined that a fix is not necessary. | |
| Title | JWT Exposure via GET Request in Edito CMS | |
| Weaknesses | CWE-598 | |
| References |
| |
| Metrics |
cvssV4_0
|
No data.
Use of HTTP Request With Sensitive Query String
No data.
No data.
No data.
No data.