# CVE-2026-10077: YOOtheme Pro < 5.0.35 - Author+ Stored XSS via UIkit Data Attributes

> Authors can inject malicious scripts via UIkit attributes in YOOtheme Pro, leading to stored XSS execution in other users' browsers.

- **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:** 2 Jul 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-76v2-c9r8-5q7q

## What is CVE-2026-10077?

CVE-2026-10077 is a medium-severity cross-site scripting vulnerability in Unknown yootheme, published on 2 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The yootheme WordPress theme before 5.0.35 does not prevent its bundled front-end framework from treating certain HTML attributes, which are permitted by wp_kses_post(), as markup, allowing users with the Author role to perform Stored Cross-Site Scripting attacks that execute in the browser of any user who views the affected post.

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


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

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

## Is CVE-2026-10077 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10077 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10077 is a medium-severity cross-site scripting vulnerability in Unknown yootheme, published on 2 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10077 exists.

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

## Sources

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

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