# CVE-2026-14921: Ultimate Addons for WPBakery Page Builder < 3.21.5 - Contributor+ Stored XSS via ult_buttons Shortcode

> Contributors can inject malicious scripts via the ult_buttons shortcode, potentially leading to code execution or account takeover.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-5rjg-8878-gjp3

## What is CVE-2026-14921?

CVE-2026-14921 is a medium-severity cross-site scripting vulnerability in Unknown Ultimate Addons for WPBakery Page Builder, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Ultimate Addons for WPBakery Page Builder WordPress plugin before 3.21.5's shared link-rendering function, Ultimate_VC_Addons::uavc_link_init(),

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

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


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

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

## Is CVE-2026-14921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14921 is a medium-severity cross-site scripting vulnerability in Unknown Ultimate Addons for WPBakery Page Builder, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, 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-14921 exists.

Affected product: Unknown Ultimate Addons for WPBakery Page Builder. 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-14921/ (Markdown: https://insights.sbomify.com/CVE-2026-14921/index.md)
```

## Sources

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

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