# CVE-2022-2516: Visual Composer Website Builder <= 45.0 - Authenticated Stored Cross-Site Scripting via 'Title'

> Authenticated attackers can inject arbitrary scripts via post titles in Visual Composer, leading to code execution when users view the page.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2022
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-f64c-c8wr-53rr

## What is CVE-2022-2516?

CVE-2022-2516 is a medium-severity cross-site scripting vulnerability in visualcomposer Visual Composer Website Builder, Landing Page Builder, Custom Theme Builder, Maintenance Mode & Coming Soon Pages, published on 6 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Visual Composer Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the post/page 'Title' value in versions up to, and including, 45.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with access to the visual composer editor to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

## Which versions are affected by CVE-2022-2516?

It affects 1 product.


Products: Visualcomposer Visual Composer Website Builder.

## How do I fix CVE-2022-2516?

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

## Is CVE-2022-2516 being exploited?

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

## Other vulnerabilities in visualcomposer Visual Composer Website Builder, Landing Page Builder, Custom Theme Builder, Maintenance Mode & Coming Soon Pages

- [CVE-2025-46254](https://insights.sbomify.com/CVE-2025-46254/): WordPress Visual Composer Website Builder plugin <= 45.10.0 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-35653](https://insights.sbomify.com/CVE-2024-35653/): Cross-site scripting in Visual Composer Website Builder (medium 6.5)
- [CVE-2023-6880](https://insights.sbomify.com/CVE-2023-6880/): Visual Composer Premium <= 45.6.0 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2022-2430](https://insights.sbomify.com/CVE-2022-2430/): Visual Composer Website Builder <= 45.0 - Authenticated Stored Cross-Site Scripting via 'Text Block' (medium 6.4)
- [CVE-2020-36722](https://insights.sbomify.com/CVE-2020-36722/): Visual Composer <= 26.0 - Multiple Cross-Site Scripting (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2516 and fix it if it is affected.

What it is: CVE-2022-2516 is a medium-severity cross-site scripting vulnerability in visualcomposer Visual Composer Website Builder, Landing Page Builder, Custom Theme Builder, Maintenance Mode & Coming Soon Pages, published on 6 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2516 in the wild and no public exploit code.

Affected product: visualcomposer Visual Composer Website Builder, Landing Page Builder, Custom Theme Builder, Maintenance Mode & Coming Soon Pages. 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-2022-2516/ (Markdown: https://insights.sbomify.com/CVE-2022-2516/index.md)
```

## Sources

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

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