# CVE-2026-87970: If-So Dynamic Content 1.8 - 1.10.1 - Reflected XSS via render_ifso_shortcodes

> Attackers can execute arbitrary JavaScript in visitors' browsers via a crafted link due to unescaped input in an AJAX response.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-4fx4-j9h4-c94x

## What is CVE-2026-87970?

CVE-2026-87970 is a medium-severity cross-site scripting vulnerability in Unknown If-So Dynamic Content, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The If-So Dynamic Content  WordPress plugin before 1.10.2 does not escape a request-supplied value before reflecting it in an unauthenticated AJAX response that is served as HTML, allowing attackers to execute arbitrary JavaScript in the browser of a visitor who opens a crafted link.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-87970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87970 is a medium-severity cross-site scripting vulnerability in Unknown If-So Dynamic Content, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-87970 in the wild and no public exploit code.

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

## Sources

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

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