# CVE-2026-77996: Joomla Extension - yootheme.com - Authenticated, privileged stored XSS in YOOtheme Pro 1.0.0-5.0.41

> Privileged users can inject malicious scripts via the location field, potentially leading to code execution or account takeover in Joomla sites using YOOtheme Pro.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/S:N/AU:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-px6v-5f2p-p6xr

## What is CVE-2026-77996?

CVE-2026-77996 is a high-severity cross-site scripting vulnerability in yootheme.com YOOtheme Pro extension for Joomla, published on 25 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Joomla Extension - yootheme.com - Authenticated, privileged stored XSS in YOOtheme Pro 1.0.0-5.0.41 - Lack of escaping in the location custom field lead to a XSS vector.

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

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


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

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

## Is CVE-2026-77996 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77996 is a high-severity cross-site scripting vulnerability in yootheme.com YOOtheme Pro extension for Joomla, published on 25 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77996 in the wild and no public exploit code.

Affected product: yootheme.com YOOtheme Pro extension for Joomla. 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-77996/ (Markdown: https://insights.sbomify.com/CVE-2026-77996/index.md)
```

## Sources

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

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