CVE-2025-8264: Versions of the package z-push/z-push-dev before 2.7.6 are vulnerable to SQL Injection due to unparameteriz...
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');
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker may abuse the login username to compromise a database connected to certain Z-Push installations. Successful exploitation could alter or delete sensitive data. Risk is limited to versions before 2.7.6 using the IMAP backend with SQL-based sender identity configuration.
Executive priority
Treat affected installations as an urgent remediation item because database integrity and connected systems may be at risk. Prioritize externally reachable deployments and those linked to sensitive databases. Validate configuration first, since unaffected backends or non-SQL identity settings materially reduce exposure.
Technical view
CVE-2025-8264 is a CWE-89 SQL injection caused by unparameterized IMAP-backend queries. Attacker-controlled basic-authentication usernames can reach the query when IMAP_FROM_SQL_QUERY is configured. The supplied CVSS 4.0 score is 9.1, reflecting potentially high integrity and downstream confidentiality, integrity, and availability impact.
Likely exposure
Exposure requires all identified conditions: z-push/z-push-dev before 2.7.6, the IMAP backend, and IMAP_FROM_SQL_QUERY configuration. Installations using the default sender configuration or LDAP are not described as affected. Internet-accessible synchronization endpoints would present greater practical exposure.
Exploitation context
The bundle identifies a remote attack path requiring no privileges or user interaction, but records CISA KEV status as false. It does not establish active exploitation in the wild. Public vulnerability research and a corrective code change are referenced, so defenders should not treat the issue as merely theoretical.
Researcher notes
The vulnerable path is reported in the IMAP identity lookup and depends on attacker-controlled basic-authentication usernames reaching an unparameterized query. Scope should be confirmed against deployed code and configuration. The bundle does not quantify attack prevalence or prove compromise; incident conclusions require local log and database evidence.
Mitigation direction
Upgrade z-push/z-push-dev to version 2.7.6 or later.
If upgrading is delayed, stop using IMAP_FROM_SQL_QUERY.
Set IMAP_DEFAULTFROM to the default empty value or LDAP, as appropriate.
Check current Z-Push vendor guidance before finalizing remediation.
Validation and detection
Inventory Z-Push versions and identify installations earlier than 2.7.6.
Confirm whether each installation actively uses the IMAP backend.
Inspect backend/imap/config.php for SQL-based sender identity configuration.
Review authentication and linked-database logs for suspicious username-related query activity.
After remediation, verify configuration and normal synchronization behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.