What is CVE-2026-59074?
Edito CMS is vulnerable to improper cryptographic signature verification in the JWT refresh logic. An authenticated low-privilege user can submit self-crafted JWT containing an existing user identifier and, due to the lack of signature validation, obtain a valid, fully-signed session token for any account in the system. This allows the attacker to impersonate any user, including administrators. This issue was fixed in version 5.10.2607. Hotfixes for older versions (5.8) have also been released.
The record classifies CVE-2026-59074 under weakness class CWE-347. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 2 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 8.7 — High (derived from score)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 8.2% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-11-13
Is CVE-2026-59074 being exploited?
It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.
Affected products and versions
- Edito: CMS
How to fix CVE-2026-59074
No vendor patch reference has been recorded for CVE-2026-59074 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-59074
1 tracked threat in the Threadlinqs corpus references CVE-2026-59074, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories.