cve.bz

CVE-2026-114189 wpvibes anywhere elementor: SQL Injection

8.5 highEPSS 0.3%Fix available

High (8.5) in wpvibes anywhere elementor. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPVibes AnyWhere Elementor anywhere-elementor allows Blind SQL Injection.This issue affects AnyWhere Elementor: from n/a through 1.3.0.

Severity

CVSS 3.1

8.5 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-114189 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114189?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114189?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114189 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-114189

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-114189](https://cve.bz/cve/badge/CVE-2026-114189.svg)](https://cve.bz/cve/CVE-2026-114189)

HTML:

<a href="https://cve.bz/cve/CVE-2026-114189"><img src="https://cve.bz/cve/badge/CVE-2026-114189.svg" alt="CVE-2026-114189"></a>

Affected

  • wpvibes:anywhere elementor

Versions

From the CNA's record in the CVE List.

ProductAffected
WPVibes AnyWhere Elementorthrough 1.3.0

Fixed in

ProductFixed in
WPVibes AnyWhere Elementor1.3.1

Fix and patched versions

  • WPVibes AnyWhere Elementor: fixed in 1.3.1

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON