CVE-2026-59080

JWT Exposure via GET Request in Edito CMS

  • Low 2.1

Description

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.

Key facts

Published
13 Nov 2026
Last changed
13 Nov 2026
Assigned by
CERT-PL
EPSS
0.113% likely to be exploited in the next 30 days, higher than 1.481% of CVEs (scores for 15 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 2.1CVSS 4.0, Lowfrom the CNA (CERT-PL)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
EditoEdito CMS
  • Default status: affected
  • 0 up to and including 5.10.2607 (affected)

Timeline

  1. 13 Nov 2026 Published

Weakness

References