CVE-2025-8264

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.0 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Versions of the package z-push/z-push-dev before 2.7.6 are vulnerable to SQL Injection due to unparameterized queries in the IMAP backend. An attacker can inject malicious commands by manipulating the username field in basic authentication. This allows the attacker to access and potentially modify or delete sensitive data from a linked third-party database. Note: This vulnerability affects Z-Push installations that utilize the IMAP backend and have the IMAP_FROM_SQL_QUERY option configured. Mitigation Change configuration to use the default or LDAP in backend/imap/config.php php define('IMAP_DEFAULTFROM', ''); or php define('IMAP_DEFAULTFROM', 'ldap');

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

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 (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2025

Last Modified

August 13, 2026

Advisory Details (4)

Auto-updated May 2, 2026
Patch available.
Web page

XBOW - When the Heat Gets to Your Database: A Refreshing SQL Injection Discovery in Z-Push

https://xbow.com/blog/xbow-zpush-sqli/
Web page

SQL Injection in z-push/z-push-dev | CVE-2025-8264 | Snyk

https://security.snyk.io/vuln/SNYK-PHP-ZPUSHZPUSHDEV-10908180
Web page

CVE-2025-8264 - Imap - update user_identity getIdentityFromSql, to use parameters to prevent SQL Injection by matidau · Pull Request #161 · Z-Hub/Z-Push · GitHub

https://github.com/Z-Hub/Z-Push/pull/161/commits/f981d515a35ac4c303959af21dce880a5db02786
Web page

CVE-2025-8264 - Imap - update user_identity getIdentityFromSql, to use parameters to prevent SQL Injection by matidau · Pull Request #161 · Z-Hub/Z-Push · GitHub

https://github.com/Z-Hub/Z-Push/pull/161

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
z-push/z-push-dev2.2.10 ... 2.7.5 (100 versions)
  • every version up to 2.7.6: fixed in 2.7.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 197 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 20:38 UTCEG score recompute
  2. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-14 14:43 UTCEG score recompute
  5. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-12 16:44 UTCEG score recompute
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-11 20:19 UTCEG score recompute
  9. 2026-10-11 18:31 UTCEG score recompute
  10. 2026-10-11 15:05 UTCEG score recompute
  11. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-07 20:35 UTCOSV refresh
  17. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 68 more
  1. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-09-18 02:36 UTCOSV refresh
  6. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-08-30 03:18 UTCOSV refresh
  22. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  26. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  29. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  30. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  31. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  32. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  33. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  34. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  36. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  38. 2026-08-13 15:35 UTCEG score recompute
  39. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  40. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  41. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  42. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  43. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  44. 2026-08-07 16:27 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  46. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  48. 2026-08-03 15:29 UTCEG score recompute
  49. 2026-08-03 15:28 UTCMITRE cvelistV5CVSS v4 → 9.1
  50. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  51. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  52. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  53. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  54. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  55. 2026-07-27 15:57 UTCOSV refresh
  56. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  57. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  58. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  59. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  60. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  61. 2026-07-23 03:03 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  64. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  65. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  66. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  67. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  68. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.4% · 31st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-8264?
CVE-2025-8264 is a critical-severity vulnerability; its CVE record was published on July 29, 2025. Versions of the package z-push/z-push-dev before 2.7.6 are vulnerable to SQL Injection due to unparameterized queries in the IMAP backend. An attacker can inject malicious commands by manipulating the username field in basic authentication. This allows the attacker to access and potentially modify…
When was the CVE record for CVE-2025-8264 published?
The CVE record for CVE-2025-8264 was published on July 29, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 13, 2026; the record at its source may have been updated since.
Is CVE-2025-8264 actively exploited?
CVE-2025-8264 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-8264?
CVE-2025-8264 has a CVSS base score of 9.0 (the CNA's own assessment, by snyk; NVD's own analysis pending).
How do I remediate CVE-2025-8264?
A fix for CVE-2025-8264 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-8264

Explore →

Is Your Infrastructure Affected by CVE-2025-8264?

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

Book a Demo →Browse All CVEs