# CVE-2026-115225: Smart Popup by Supsystic < 2.0.2 - Unauthenticated SSRF via MailChimp Groups Lookup


- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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-4r9j-p4gw-x3hm

## What is CVE-2026-115225?

CVE-2026-115225 is a medium-severity vulnerability in Unknown Customer Engagement System, published on 28 Oct 2026. 

### Official description

The Customer Engagement System  WordPress plugin before 2.0.2 does not restrict access to its MailChimp interest-group lookup or validate the API key supplied to it, allowing unauthenticated users to make the server open connections to arbitrary internal hosts and ports and infer from response timing which ones are reachable.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-115225 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115225 is a medium-severity vulnerability in Unknown Customer Engagement System, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115225 in the wild and no public exploit code.

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

## Sources

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

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