Web Push Notifications – Webpushr
Approved changes feed: RSS · Atom
cpe:2.3:a:webpushr:web_push_notifications_–_webpushr:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Webpushr (054996a4-50b1-5b78-ae52-74f1f6cf4ea5) |
|---|---|
| Product | Web Push Notifications – Webpushr (4e45668e-bd86-57e6-9d76-b772183114f3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-9729 |
vulnerable | 2026-07-29 01:12:09.597742 |
Web Push Notifications <= 4.39.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'webpushr_notification_title' Post Meta Parameter
MEDIUM (6.4)
The Webpushr Push Notifications plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'webpushr_notification_title' and 'webpushr_notification_body' parameters in versions up to, and including, 4.39.0. This is due to insufficient input sanitization in the save_send_notification_flag() function and missing output escaping in the wpp_notification_box() function, which concatenates raw post meta values directly into HTML attribute and textarea contexts. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Published: 2026-07-23T06:52:33.814Z
Updated: 2026-07-23T16:04:51.114Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.