# CVE-2026-114188: WPVibes AnyWhere Elementor stored cross-site scripting

Source: https://junglewise.ai/threats/cve-2026-114188-improper-neutralization-of-input-during-web-page-generation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-114188 · Severity: medium · CVSS 6.5 · Published 2026-11-08

WPVibes AnyWhere Elementor is a WordPress plugin that extends the Elementor page builder with additional functionality. The plugin contains a stored cross-site scripting (XSS) vulnerability that allows attackers with subscriber-level access to inject malicious scripts into the site, which can then steal visitor data or hijack user accounts when those pages are viewed.

Technologies: [WPVibes AnyWhere Elementor](https://junglewise.ai/threats/technologies/anywhere-elementor). Vendors: [WPVibes](https://junglewise.ai/threats/vendors/wpvibes).

## Quick answers

**Is CVE-2026-114188 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-114188 being exploited in the wild.

**How severe is CVE-2026-114188?** Medium severity, with a CVSS score of 6.5, published 8 November 2026.

**Which products and versions are affected?** WPVibes AnyWhere Elementor through 1.3.0.

**Is there a fix for CVE-2026-114188?** Yes: fixed in 1.3.1 and later. Until then: Until you can update to version 1.3.1 or later, restrict subscriber-level access to users who need it and consider using Patchstack's mitigation rule to block exploitation attempts. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-114188 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-114188?** Check whether you run WPVibes AnyWhere Elementor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 1.3.1 and later

Until you can update to version 1.3.1 or later, restrict subscriber-level access to users who need it and consider using Patchstack's mitigation rule to block exploitation attempts.

## Technical details

The vulnerability is an improper neutralization of user input during web page generation, classified as stored XSS. It affects the AnyWhere Elementor plugin through version 1.3.0 and requires subscriber-level privileges and user interaction (such as the victim clicking a link or visiting a crafted page) to exploit. The injected malicious scripts persist in the site and execute for all visitors who view the affected content.

## Affected products

- WPVibes AnyWhere Elementor through 1.3.0

## Timeline

- 2026-11-06: disclosed
- 2026-11-08: advisory

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://patchstack.com/database/wordpress/plugin/anywhere-elementor/vulnerability/wordpress-anywhere-elementor-plugin-1-3-0-cross-site-scripting-xss-vulnerability-2?_s_id=cve](https://patchstack.com/database/wordpress/plugin/anywhere-elementor/vulnerability/wordpress-anywhere-elementor-plugin-1-3-0-cross-site-scripting-xss-vulnerability-2?_s_id=cve)

## Related threats

- [WPVibes AnyWhere Elementor SQL injection](https://junglewise.ai/threats/cve-2026-114189-improper-neutralization-of-special-elements-used-in-an-sql)
- [WPVibes AnyWhere Elementor broken access control in configuration pages](https://junglewise.ai/threats/cve-2026-114186-missing-authorization-vulnerability-in-wpvibes-anywhere)
- [WPVibes AnyWhere Elementor broken access control](https://junglewise.ai/threats/cve-2026-119467-missing-authorization-vulnerability-in-wpvibes-anywhere)
- [WPVibes AnyWhere Elementor broken access control](https://junglewise.ai/threats/cve-2026-114187-missing-authorization-vulnerability-in-wpvibes-anywhere)
- [WPVibes AnyWhere Elementor stored cross-site scripting](https://junglewise.ai/threats/cve-2026-114185-improper-neutralization-of-input-during-web-page-generation)