Skip to main content
VulnerabilityPublished

CVE-2026-92923: Unlimited Elements for Elementor (WordPress plugin) · SQL Injection

Affects Unlimited Elements for Elementor (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.0.21 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.21
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Unlimited Elements for Elementor (WordPress plugin) to 2.0.21.

Affected software

ProductAffectedFixed in
Unlimited Elements for ElementorAffected
  • >=1.5.142 <2.0.21
Fixed in
  • 2.0.21

AI-suggested

Upgrade the Unlimited Elements for Elementor plugin to version 2.0.21 or later, where the vulnerability is fixed. Versions prior to 2.0.21 are vulnerable. No other mitigation steps are indicated in the available data.

Description

The Unlimited Elements for Elementor WordPress plugin before 2.0.21 does not sanitise and escape a parameter before using it in a SQL statement, allowing users with a role as low as subscriber to perform blind SQL injection attacks and read arbitrary data from the database. Version 2.0.18 removed the subscriber-level access, so from 2.0.18 onward the issue requires a Contributor role or above.

References

Community reviews

Loading reviews…