CVE-2026-59080: JWT Exposure via GET Request in Edito CMS

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by CERT-PL, published 2026-11-13).

Weakness: CWE-598 Use of GET request method with sensitive query strings

How it can be exploited

Exploitable with local access with low attack complexity only when specific conditions are present needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability low. 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

Public exploit evidence (Exploit Observer)

Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.

Live scores

EPSS
0.001
low predicted chance of attack
VEDAS
0.048
little exploit evidence
On CISA KEV
Not listed
Detection rule
Out of scope (local)
EPSS (chance of attack)
100.1CVE-2026-59080 EPSS over time2026-112026-11-17
VEDAS (exploit evidence)
100.5CVE-2026-59080 VEDAS over time2026-112026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Edito CMSup to and including 5.10.2607Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.

Advisories on this CVE

References

Technical analysis and advisories

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners