CVE-2026-59080: JWT Exposure Through GET Request Query Strings in Edito CMS
Edito CMS versions through 5.10.2607 transmit JSON Web Tokens (JWTs) in GET request query strings, exposing authentication tokens through browser history. A local attacker with access to the victim's browser history can recover and reuse a still-valid token to perform actions as the victim. Exploitation is time-limited because the tokens have a short validity period.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows impersonation of the victim and unauthorized actions within the victim's account permissions until the exposed JWT expires. The vendor assessed the likelihood of exploitation as very low because the tokens are short-lived.
Mitigation
If you can’t patch tonight, do this now.
Restrict access to users' browser profiles and browser history, particularly on shared workstations, and lock unattended sessions. Removing affected history entries can reduce subsequent exposure but does not invalidate tokens already obtained. Short token lifetimes limit, but do not eliminate, the opportunity for misuse.
Remediation
Patch, then assume compromise.
No fix is available for this vulnerability in versions through 5.10.2607. The vendor determined that a fix was unnecessary because the assessed likelihood of exploitation was very low.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-59080 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-59080 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-59080?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-59080.
- Is there a patch for CVE-2026-59080?
- No fix is available for this vulnerability in versions through 5.10.2607. The vendor determined that a fix was unnecessary because the assessed likelihood of exploitation was very low.
- How severe is CVE-2026-59080?
- CVE-2026-59080 has a CVSS v4 score of 2.1 (Low) and an EPSS score of 0.11% (1st percentile) as of Nov 17, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.