Skip to main content

Elementor Website Builder CVE-2026-62062

| EUVDEUVD-2026-86532 HIGH
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-09-25 Patchstack GHSA-f746-2pfg-cwp9
8.8
CVSS 3.1 · Vendor: Patchstack
Share

Severity by source

Vendor (Patchstack) PRIMARY
8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI
5.4 MEDIUM

Network CSRF needs no attacker auth (PR:N) but requires admin interaction (UI:R); impact downgraded to C:L/I:L/A:N as the vague description does not substantiate the full C:H/I:H/A:H triad.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Sep 25, 2026 - 07:05 vuln.today
CVE Published
Sep 25, 2026 - 06:29 cve.org
HIGH 8.8

DescriptionCVE.org

Cross-Site Request Forgery (CSRF) vulnerability in Elementor Website Builder allows Cross Site Request Forgery.

This issue affects Elementor Website Builder: from n/a through 4.3.1.

AnalysisAI

Cross-site request forgery in Elementor Website Builder (all versions through 4.3.1) lets a remote attacker who holds no credentials of their own induce a logged-in WordPress administrator into silently executing unintended state-changing actions inside the victim's authenticated session. Exploitation requires both a privileged user to be authenticated and that user to be lured onto attacker-controlled content (CVSS UI:R), which caps practical severity despite the high base score of 8.8 reported by the researcher; our independent assessment scores the same vector at C:L/I:L/A:N because the achievable action set is not fully characterised in the advisory. …

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

No credit card · 7-day full trial

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Requires a logged-in Elementor/WordPress administrator (or privileged user) to be tricked into visiting attacker-controlled content while their session is active (UI:R) - the CSRF fires in the victim's authenticated context, so the attacker themselves needs no credentials (PR:N). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H = 8.8 High) reflects a network-reachable, unauthenticated CSRF that nonetheless REQUIRES victim interaction (UI:R) - a logged-in administrator must be tricked into visiting a malicious page or clicking a crafted link. … 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 Vendor-released patch: not confirmed in the supplied data - the advisory only states the affected range ends at 4.3.1, implying a correction in a later release, so treat "upgrade Elementor Website Builder beyond 4.3.1 to the current stable version" as the primary action and verify the exact fixed build against the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/elementor/vulnerability/wordpress-elementor-website-builder-plugin-4-3-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve) before assuming coverage; use a staged update given that Elementor changes carry layout-regression risk. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, inventory every WordPress instance running Elementor Website Builder, confirm the installed version, and treat every deployment at version 4.3.1 or earlier as affected; restrict wp-admin access to trusted networks or VPN, enforce multi-factor authentication for all administrator accounts, and deploy WAF or reverse-proxy rules that validate Origin/Referer headers and require anti-CSRF tokens on state-changing admin requests. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-62062 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy