# CVE-2026-59080: JWT Exposure via GET Request in Edito CMS

Status: published. Published: 2026-11-13. Updated: 2026-11-13.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Edito / Edito CMS: ≥ 0; ≤ 5.10.2607 (affected, semver). Source: CNA: CERT-PL

## Severity and prioritization

- CVSS 4.0: 2.1 (low); 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; source: CNA: CERT-PL

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-598

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://cert.pl/posts/2026/11/CVE-2026-59081 (CNA: CERT-PL; third-party-advisory)

- https://www.edito.pl/ (CNA: CERT-PL; product)

## Provenance

- CNA: CERT-PL: https://www.cve.org/CVERecord?id=CVE-2026-59080; retrieved 2026-11-13; source updated 2026-11-13

Revision: 513fde81376beddd5b0d3ee751207afc858afb24b331ea1b98c63c60a08f1291

Canonical: https://y2.dev/cve/CVE-2026-59080

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.