LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0816: All push notification for WP <= 1.5.3 - Authenticated (Administrator+) SQL Injection via 'delete_id' Parameter

The All push notification for WP plugin for WordPress is vulnerable to time-based SQL Injection via the 'delete_id' parameter in all versions up to, and including, 1.5.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0816 affects the WordPress plugin “All push notification for WP” up to version 1.5.3. An attacker who already has administrator-level access could abuse a plugin parameter to read sensitive database information. This is not a remote unauthenticated issue, so urgency is lower than many SQL injection flaws, but exposed admin accounts increase risk.

Executive priority

Treat as a targeted cleanup item, not an emergency internet-wide fire drill. Prioritize sites where administrators are numerous, shared, or externally managed, and where the WordPress database contains sensitive customer or business data.

Technical view

The plugin is vulnerable to time-based SQL injection through the delete_id parameter because user input is not sufficiently escaped or prepared in an SQL query. CVSS 3.1 is 4.9 with high privileges required and high confidentiality impact. The issue is classified as CWE-89 and affects versions up to and including 1.5.3 per the CVE description.

Likely exposure

WordPress sites using All push notification for WP version 1.5.3 or earlier are the likely exposure. Exploitation requires an authenticated administrator or higher-privileged account, limiting exposure to compromised, malicious, or misused admin sessions.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not listed as KEV in the supplied bundle. The practical risk is highest where WordPress administrator accounts are shared, weakly protected, or already compromised.

Researcher notes

Evidence is limited to the CVE/Wordfence description and WordPress Trac code references. The bundle does not name a patched version or confirm exploitation in the wild. Avoid assuming unauthenticated reachability; the stated prerequisite is administrator-level authentication.

Mitigation direction

  • Inventory WordPress sites for the All push notification for WP plugin.
  • Identify plugin versions and prioritize any installation at 1.5.3 or earlier.
  • Check the plugin vendor, WordPress.org, and Wordfence guidance for an available fix.
  • Restrict and monitor WordPress administrator access until remediation is confirmed.
  • Remove the plugin if it is unnecessary and no trusted fix is available.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the installed plugin version from WordPress administration or asset inventory.
  • Review administrator account activity for unusual plugin actions or database-related errors.
  • Check web and application logs for suspicious requests involving delete_id.
  • Verify remediation against vendor or WordPress.org release information.
Prepared
Confidence
high
Sources
5

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.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0816 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2026-0816Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gtlwpdevAll push notification for WP0unaffected
Weakness

CWE details

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.