Skip to main content
Mallory
LowVulnerability

CVE-2026-59080: JWT Exposure Through GET Request Query Strings in Edito CMS

Published Nov 13, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 3 in a dayToday
CVSS2.1Low · v4
EPSS0.11%1st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-59080CWE-598 · Use of HTTP Request With Sensitive…

Edito CMS versions through 5.10.2607 transmit JSON Web Tokens (JWTs) in GET request query strings, exposing authentication tokens through browser history. A local attacker with access to the victim's browser history can recover and reuse a still-valid token to perform actions as the victim. Exploitation is time-limited because the tokens have a short validity period.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows impersonation of the victim and unauthorized actions within the victim's account permissions until the exposed JWT expires. The vendor assessed the likelihood of exploitation as very low because the tokens are short-lived.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to users' browser profiles and browser history, particularly on shared workstations, and lock unattended sessions. Removing affected history entries can reduce subsequent exposure but does not invalidate tokens already obtained. Short token lifetimes limit, but do not eliminate, the opportunity for misuse.

Remediation

Patch, then assume compromise.

No fix is available for this vulnerability in versions through 5.10.2607. The vendor determined that a fix was unnecessary because the assessed likelihood of exploitation was very low.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-59080 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-59080 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59080?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-59080.
Is there a patch for CVE-2026-59080?
No fix is available for this vulnerability in versions through 5.10.2607. The vendor determined that a fix was unnecessary because the assessed likelihood of exploitation was very low.
How severe is CVE-2026-59080?
CVE-2026-59080 has a CVSS v4 score of 2.1 (Low) and an EPSS score of 0.11% (1st percentile) as of Nov 17, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.