JWT Exposure via GET Request in Edito CMS

published 2026-11-13 2d ago modified 2026-11-13 yesterday also EUVD-2026-124882

cvss: 2.1; version 4.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits: 0; none known

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.

Is CVE-2026-59080 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by	version	score	vector
CNA	4.0	2.1	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
CNA	4.0	2.1	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

Affected products

Edito Edito CMS

Classification

Weakness

CWE-598 Use of HTTP Request With Sensitive Query String

References

cert.pl /posts/2026/11/CVE-2026-59081
third-party-advisory
edito.pl /
product

Sources

CVE List CVE-2026-59080
NVD CVE-2026-59080

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.