What is the CVSS score of CVE-2026-105064?

CVE-2026-105064 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.2%.

Unlimited Elements CVE-2026-105064

EUVD-2026-92330 MEDIUM

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') (CWE-470)

2026-10-05 Patchstack

GHSA-2ff7-6h2m-wxm2

WordPress Code Injection Unlimited Elements For Elementor Free Widgets Addons Templates Wordpress Plugin Unlimited Elements

6.5

CVSS 3.1 · Vendor: Patchstack

Severity by source

Vendor (Patchstack) PRIMARY

6.5 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

vuln.today AI

6.5 MEDIUM

Network-reachable, low-complexity flaw but a low-privileged authenticated account is required (PR:L); impact is confidentiality-only per description, so I:N and A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Oct 05, 2026 - 09:38 vuln.today

CVE Published

Oct 05, 2026 - 08:59 cve.org

MEDIUM 6.5

DescriptionCVE.org

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Parameter Injection.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.22.

AnalysisAI

Unsafe reflection (CWE-470) in the Unlimited Elements For Elementor (Free Widgets, Addons, Templates) WordPress plugin through version 2.0.22 lets a low-privileged authenticated account steer which class or code the plugin loads, exposing information that account should not be able to read. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, score 6.5) confirms the attacker must hold a valid WordPress login with at least low privileges, that no user interaction is required, and that impact is limited to confidentiality with no integrity or availability effect. …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

technique details hidden

Exploit

technique details hidden

Execution

technique details hidden

Impact

technique details hidden

Access

technique details hidden

Exploit

technique details hidden

Execution

technique details hidden

Impact

technique details hidden

Vulnerability AssessmentAI

Exploitation	Requires a valid authenticated WordPress account with at least low privileges (PR:L) on a site running the Unlimited Elements For Elementor plugin at version 2.0.22 or earlier; the plugin must be installed and active. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	This is a moderate-severity, authenticated information-disclosure issue rather than a top-priority emergency. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation	The provided intelligence does not state a fixed version, so begin by consulting the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/unlimited-elements-for-elementor/vulnerability/wordpress-unlimited-elements-for-elementor-free-widgets-addons-templates-plugin-2-0-22-broken-access-control-vulnerability?_s_id=cve) and the plugin's changelog to identify the release in which the issue is resolved, then upgrade to that version or to the current latest release; because the affected range runs through 2.0.22, any site still on 2.0.22 or earlier should be treated as vulnerable until a fix is confirmed and applied. … Detailed patch versions, workarounds, and compensating controls in full report.