CVE-2026-59080 · Other
NO FIX YET
Edito CMS places its JWT token in GET request URLs, so the token is stored in browser history. A local attacker who reads that history can reuse the short-lived token to act as the victim until it expires.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run Edito CMS and let users sign in from shared or unmanaged machines may be exposed, since the risk depends on local access to browser history. The sources do not name affected versions. The vendor says a fix is not necessary, and the token expires after a short period.
Not affected if no-shared-machines, token-expires-quickly
Who cares edito-cms, self-hosted
Unknown from the sources.
No fix yet, per the sources.
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.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.