# CVE-2026-17005: Horizontal Scrolling Announcements <= 2.6 - Contributor+ Stored XSS via Style Field

> Contributors can inject malicious scripts via announcement settings, 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:** 4 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-6g7j-p76q-h89g

## What is CVE-2026-17005?

CVE-2026-17005 is a medium-severity cross-site scripting vulnerability in Unknown Horizontal scrolling announcements, published on 4 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Horizontal scrolling announcements WordPress plugin through 2.6 does not sanitise and escape one of its announcement settings before outputting it into an attribute context on the front end, allowing users granted access to the announcement management page (Contributor and above, once permitted) to perform Stored Cross-Site Scripting attacks that execute in the browser of anyone viewing the announcement.

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

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


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

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

## Is CVE-2026-17005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17005 is a medium-severity cross-site scripting vulnerability in Unknown Horizontal scrolling announcements, published on 4 Oct 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-17005 in the wild and no public exploit code.

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

## Sources

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

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