CVE-2026-0816
Time-Based SQL Injection in All Push Notification Plugin
Publication date: 2026-02-04
Last updated on: 2026-02-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | all_push_notification | to 1.5.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The All push notification for WP plugin for WordPress is vulnerable to a time-based SQL Injection via the 'delete_id' parameter in all versions up to and including 1.5.3. This vulnerability arises because the plugin does not properly escape the user-supplied 'delete_id' parameter and fails to sufficiently prepare the existing SQL query. As a result, authenticated attackers with administrator-level access or higher can append additional SQL queries to the existing ones.
This allows attackers to extract sensitive information from the database by exploiting the SQL Injection vulnerability.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an authenticated administrator-level attacker to execute additional SQL queries on your WordPress database. This can lead to unauthorized extraction of sensitive information stored in the database.
Since the attack requires administrator-level access, it assumes the attacker already has significant privileges, but it can still be used to escalate data exposure beyond intended limits.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a time-based SQL Injection via the 'delete_id' parameter in the All Push Notification WordPress plugin versions up to 1.5.3. Detection would involve monitoring for suspicious SQL queries or attempts to exploit the 'delete_id' parameter, especially from authenticated users with administrator-level access.
Since the vulnerability requires authenticated administrator access, detection can include reviewing WordPress admin logs for unusual activity related to push notification deletions.
Specific commands to detect exploitation attempts are not provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the All Push Notification plugin to a version later than 1.5.3 where the vulnerability is fixed.
If an update is not immediately available, restrict administrator-level access to trusted users only, and monitor for suspicious activity involving the 'delete_id' parameter.
Additionally, consider disabling or removing the vulnerable plugin until a patched version is installed.