# CVE-2026-5077: Cross-site scripting in Total

> Authenticated attackers can inject arbitrary scripts via post titles in the Total WordPress theme, leading to code execution when pages are viewed.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-5gp4-hrgf-7vj6

## What is CVE-2026-5077?

CVE-2026-5077 is a medium-severity cross-site scripting vulnerability in hashthemes Total, published on 2 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Total theme for WordPress is vulnerable to Stored Cross-Site Scripting via post titles in versions up to, and including, 2.2.1 due to insufficient output escaping when rendering the_title() inside HTML attribute context in the home blog section template. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the malicious post to be published and displayed with a featured image in the Home Page blog section.

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

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


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

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

## Is CVE-2026-5077 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5077 is a medium-severity cross-site scripting vulnerability in hashthemes Total, published on 2 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5077 in the wild and no public exploit code.

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

## Sources

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

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