CVE-2026-18322 json
Smart Popup by Supsystic <= 1.12.0 - Unauthenticated Privilege Escalation to Administrator
published 2026-08-05 3 mo ago modified 2026-08-12 2 mo ago also EUVD-2026-53039
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
The Smart Popup by Supsystic plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.12.0. This is due to a permission map collision in the `havePermissions()` function in `classes/frame.php`, where `array_merge()` overwrites the popup module's administrator-restricted method list with the base controller's value, silently removing `save` from protected actions; this is compounded by the subscription confirmation email embedding the same generic `pps_nonce` that the unauthenticated `wp_ajax_nopriv_save` endpoint accepts, and by the complete absence of any server-side role allowlist in `createWpSubscriber()`. This makes it possible for unauthenticated attackers to submit a crafted POST request to `admin-ajax.php` using a nonce obtained from a public subscription confirmation email, setting `params[tpl][sub_wp_create_user_role]` to `administrator` via the exposed `popupControllerPps::save()` action, and then triggering the stored confirmation flow to create a persistent WordPress Administrator account with attacker-chosen credentials.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3 mo ago
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- supsysticcom Smart Popup by Supsystic
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/835579b0-8a96-40fa-a6a3-30571a0a1d0a?source=cve
- plugins.trac.wordpress.org /browser/popup-by-supsystic/tags/1.11.2/classes/frame.php#L180
- plugins.trac.wordpress.org /browser/popup-by-supsystic/tags/1.11.2/modules/subscribe/models/subscribe.php#L440
- plugins.trac.wordpress.org /browser/popup-by-supsystic/tags/1.11.2/modules/subscribe/models/subscribe.php#L292
- plugins.trac.wordpress.org /browser/popup-by-supsystic/tags/1.11.2/modules/popup/models/popup.php#L316
- plugins.trac.wordpress.org /browser/popup-by-supsystic/tags/1.11.2/modules/subscribe/models/subscribe.php#L358
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&new=3629986%40popup-by-supsystic%2Ftrunk%2Fmodules%2Fsubscribe%2Fmo
Sources
- CVE List CVE-2026-18322
- NVD CVE-2026-18322
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.