Skip to main content
VulnerabilityPublished

CVE-2026-59080: Edito CMS · Use of HTTP Request With Sensitive Query String

Affects Edito CMSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.1 Low.

Data as of 13 Nov 2026, 07:56 UTC

CVSS 4.0 base score
2.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CERT-PL)CVSS 4.02.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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
EditoEdito CMSAffected
  • <=5.10.2607
Fixed in–

AI-suggested

The vendor has assessed the likelihood of exploitation as very low and determined that a fix is not necessary. No specific remediation actions are required according to the vendor advisory.

Description

Edito CMS versions up to 5.10.2607 send JWT tokens via HTTP GET requests, exposing them in browser history. This exposure allows a local attacker with access to the victim's browser history to obtain a valid JWT token and perform actions on behalf of the victim. The token validity is limited to a short time period, after which it expires and cannot be used. The vendor considers the likelihood of exploitation very low and has determined that a fix is not necessary.

References

Community reviews

Loading reviews…