# CVE-2026-110524: Copy Anything to Clipboard < 5.5.5 - Contributor+ Stored XSS via 'success-text' Shortcode Attribute


- **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
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-m4h7-mwp4-h59c

## What is CVE-2026-110524?

CVE-2026-110524 is a medium-severity vulnerability in Unknown Copy Anything to Clipboard for WordPress, published on 28 Oct 2026. 

### Official description

The Copy Anything to Clipboard for WordPress  WordPress plugin before 5.5.5 does not sanitize and escape a shortcode attribute before storing it and writing it back into the page through a client-side script, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks against higher-privileged users who view and interact with the content.

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

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


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

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

## Is CVE-2026-110524 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110524 is a medium-severity vulnerability in Unknown Copy Anything to Clipboard for WordPress, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110524 in the wild and no public exploit code.

Affected product: Unknown Copy Anything to Clipboard for WordPress. 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-110524/ (Markdown: https://insights.sbomify.com/CVE-2026-110524/index.md)
```

## Sources

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

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