# CVE-2026-96899: Optima Express 8.6.0 - 8.7.5 - Author+ Stored XSS via faq_script

> Authors can inject malicious scripts via the faq_script field in Optima Express IDX, leading to stored XSS attacks against site visitors.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-xprw-377p-8v85

## What is CVE-2026-96899?

CVE-2026-96899 is a medium-severity cross-site scripting vulnerability in Unknown Optima Express IDX, published on 27 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Optima Express IDX WordPress plugin before 8.7.6 does not properly neutralise a script value submitted through one of its REST endpoints before storing it and echoing it into the document head when the post is rendered, allowing users with a role as low as author to perform Stored Cross-Site Scripting attacks.

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

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


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

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

## Is CVE-2026-96899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96899 is a medium-severity cross-site scripting vulnerability in Unknown Optima Express IDX, published on 27 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-96899 in the wild and no public exploit code.

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

## Sources

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

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