CVE-2026-27593

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Statmatic is a Laravel and Git powered content management system (CMS). Prior to versions 6.3.3 and 5.73.10, an attacker may leverage a vulnerability in the password reset feature to capture a user's token and reset the password on their behalf. The attacker must know the email address of a valid account on the site, and the actual user must blindly click the link in their email even though they didn't request the reset. This has been fixed in 6.3.3 and 5.73.10.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

February 24, 2026

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Account takeover via password reset link injection · Advisory · statamic/cms · GitHub

Affected: 6.7.1 and 5.73.10.

https://github.com/statamic/cms/security/advisories/GHSA-jxq9-79vj-rgvw
github_release Patch Available

v6.3.3

Patch available: statamic/cms v6.3.3

https://github.com/statamic/cms/releases/tag/v6.3.3
github_release Patch Available

v5.73.10

Patch available: statamic/cms v5.73.10

https://github.com/statamic/cms/releases/tag/v5.73.10
github_commit

commit b2be592ddfb5 (statamic/cms)

Fix landed in statamic/cms commit b2be592ddfb5 — awaiting tagged release

https://github.com/statamic/cms/commit/b2be592ddfb588bcb88c9be454f3590e14b145b0
github_commit Patch Available

commit 78e63dfcf705 (statamic/cms)

Patch available: statamic/cms v6.12.0 (contains commit 78e63dfcf705)

https://github.com/statamic/cms/commit/78e63dfcf705b116d5ac0f7f7f5a1a69be63d1be
github_commit

commit 6fdd03324982 (statamic/cms)

Fix landed in statamic/cms commit 6fdd03324982 — awaiting tagged release

https://github.com/statamic/cms/commit/6fdd03324982848e8754f2edd2265262d361714e

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
statamic/cmsv6.0.0 ... v6.7.0 (47 versions)6.7.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-31 17:04 UTCOSV refresh
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 34 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 09:05 UTCEG score recompute
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 01:04 UTCEG score recompute
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-12 00:49 UTCEG score recompute
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-11 06:29 UTCEG score recompute
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 20:56 UTCEG score recompute
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 08:42 UTCEG score recompute
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-07 20:48 UTCEG score recompute
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 03:03 UTCEG score recompute
  24. 2026-08-05 19:17 UTCEPSS rescore
  25. 2026-08-04 15:10 UTCEPSS rescore
  26. 2026-08-04 05:56 UTCEG score recompute
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 19:39 UTCEG score recompute
  29. 2026-08-02 02:26 UTCEPSS rescore
  30. 2026-08-01 04:16 UTCEPSS rescore
  31. 2026-07-30 16:27 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-28 15:36 UTCEPSS rescore
  34. 2026-07-27 14:07 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27593?
CVE-2026-27593 is a high vulnerability published on February 24, 2026. Statmatic is a Laravel and Git powered content management system (CMS). Prior to versions 6.3.3 and 5.73.10, an attacker may leverage a vulnerability in the password reset feature to capture a user's token and reset the password on their behalf. The attacker must know the email address of a valid…
When was CVE-2026-27593 disclosed?
CVE-2026-27593 was first published in the National Vulnerability Database on February 24, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27593 actively exploited?
CVE-2026-27593 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-27593?
CVE-2026-27593 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-27593?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27593, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27593

Explore →

Is Your Infrastructure Affected by CVE-2026-27593?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs