# CVE-2026-18322: Smart Popup by Supsystic <= 1.12.0 - Unauthenticated Privilege Escalation to Administrator

> Unauthenticated attackers can create administrator accounts via a permission collision and nonce reuse in the Smart Popup by Supsystic WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-m4qm-m3w3-jjcg

## What is CVE-2026-18322?

CVE-2026-18322 is a high-severity vulnerability in supsysticcom Smart Popup by Supsystic, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-18322?


## How do I fix CVE-2026-18322?

No fix has been published for CVE-2026-18322 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18322 being exploited?

There is no known exploitation of CVE-2026-18322 in the wild and no public exploit code.

Public exploit code:

- https://github.com/I3IT/CVE-2026-18322 (github_poc): https://github.com/I3IT/CVE-2026-18322

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18322 and fix it if it is affected.

What it is: CVE-2026-18322 is a high-severity vulnerability in supsysticcom Smart Popup by Supsystic, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18322 in the wild and no public exploit code.

Affected product: supsysticcom Smart Popup by Supsystic. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18322/ (Markdown: https://insights.sbomify.com/CVE-2026-18322/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18322
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18322
- OSV: https://osv.dev/vulnerability/CVE-2026-18322

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18322/
Summaries are generated and may contain mistakes; the official description above is the record.