Popup Builder
Approved changes feed: RSS · Atom
cpe:2.3:a:sygnoos:popup-builder:*:*:*:*:*:wordpress:*:*
part: a version: * update: *
| Vendor | Sygnoos (ce95517c-e175-5921-9d49-ee04c5e84561) |
|---|---|
| Product | Popup Builder (d96a29b4-c4bd-5d17-8e0f-28d0cbea8710) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/abidi12/popup-builder |
purl2cpe | 2026-06-01 10:15:30.519356 |
pkg:github/kagg-design/popup-builder |
purl2cpe | 2026-06-01 10:15:30.519358 |
pkg:github/wp-plugins/popup-builder |
purl2cpe | 2026-06-01 10:15:30.519359 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-10196 |
vulnerable | 2026-06-08 05:16:34.860491 |
Details available
An XSS vulnerability in the popup-builder plugin before 3.64.1 for WordPress allows remote attackers to inject arbitrary JavaScript into existing popups via an unsecured ajax action in com/classes/Ajax.php. It is possible for an unauthenticated attacker to insert malicious JavaScript in several of the popup's fields by sending a request to wp-admin/admin-ajax.php with the POST action parameter of sgpb_autosave and including additional data in an allPopupData parameter, including the popup's ID (which is visible in the source of the page in which the popup is inserted) and arbitrary JavaScript which will then be executed in the browsers of visitors to that page. Because the plugin functionality automatically adds script tags to data entered into these fields, this injection will typically bypass most WAF applications.
Published: 2020-03-13T15:48:55.000Z
Updated: 2024-08-04T10:58:38.986Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-10195 |
vulnerable | 2026-06-08 05:16:34.859422 |
Details available
The popup-builder plugin before 3.64.1 for WordPress allows information disclosure and settings modification, leading to in-scope privilege escalation via admin-post actions to com/classes/Actions.php. By sending a POST request to wp-admin/admin-post.php, an authenticated attacker with minimal (subscriber-level) permissions can modify the plugin's settings to allow arbitrary roles (including subscribers) access to plugin functionality by setting the action parameter to sgpbSaveSettings, export a list of current newsletter subscribers by setting the action parameter to csv_file, or obtain system configuration information including webserver configuration and a list of installed plugins by setting the action parameter to sgpb_system_info.
Published: 2020-03-13T15:48:58.000Z
Updated: 2024-08-04T10:58:39.016Z |
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.