# CVE-2026-115223: Smart Popup by Supsystic < 2.0.2 - Admin+ SSTI via Popup Text Block


- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-mpjc-mm6h-74q4

## What is CVE-2026-115223?

CVE-2026-115223 is a medium-severity vulnerability in Unknown Smart Popup by Supsystic, published on 28 Oct 2026. 

### Official description

The Smart Popup by Supsystic WordPress plugin before 2.0.2 does not prevent template-injection payloads from being stored in a popup text block and later evaluated by its template engine, because the filter meant to strip template delimiters runs before a decoding step that reconstructs them, allowing an authenticated administrator to execute arbitrary template expressions server-side and read PHP constants such as the site's database credentials and authentication keys.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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


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

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

## Is CVE-2026-115223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115223 is a medium-severity vulnerability in Unknown Smart Popup by Supsystic, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115223 in the wild and no public exploit code.

Affected product: Unknown 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-115223/ (Markdown: https://insights.sbomify.com/CVE-2026-115223/index.md)
```

## Sources

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

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