Skip to main content
VulnerabilityPublished

CVE-2026-59074: Edito CMS is vulnerable to improper cryptographic signature verification in the JWT refresh logic

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-59074· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 5.10.2607 soon.

Data as of 13 Nov 2026, 10:15 UTC

CVSS 4.0 base score
8.7High
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.08.7
Patch
Available – fixed in 5.10.2607
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

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 13 Nov 2026.

What to do

Upgrade Edito CMS to 5.10.2607.

Affected software

ProductAffectedFixed in
EditoEdito CMSAffected
  • <5.10.2607
Fixed in
  • 5.10.2607

AI-suggested

Upgrade Edito CMS to version 5.10.2607 or apply the available hotfixes for version 5.8 to remediate the vulnerability. These updates fix the improper signature verification in the JWT refresh logic. No other mitigation is indicated by the vendor advisory.

Description

Edito CMS contains a vulnerability in its JWT refresh logic where cryptographic signature verification is improperly performed. This flaw allows an authenticated low-privilege user to craft a JWT with an existing user identifier and bypass signature validation to obtain a valid session token for any user account, including administrators. The vulnerability is fixed in version 5.10.2607, with hotfixes available for older 5.8 versions.

References

Community reviews

Loading reviews…