Skip to main content

Avada Core EUVDEUVD-2026-48083

| CVE-2026-65471 CRITICAL
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-07-23 Patchstack GHSA-92mf-w334-37r6
9.6
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Host malicious CSRF page
  2. Delivery
    Lure authenticated admin to visit
  3. Exploit
    Browser submits forged request with cookies
  4. Execution
    Missing nonce check accepts request
  5. Impact
    Privileged action executed as victim

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated WordPress user - typically an administrator with access to the vulnerable Avada Core action - to be tricked into visiting attacker-controlled content while their session is active (UI:R is present in the CVSS vector). No attacker authentication is needed (PR:N), and attack complexity is low (AC:L). Limiting factors: the victim must hold sufficient privileges for the targeted action, must be logged in at the time, and must perform the interaction; the description does not name the exact vulnerable feature/endpoint or parameter, so the precise action that gets forged is not confirmed from available data. The plugin must be installed at version 5.15.6 or earlier.

Impact

The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H = 9.6) is aggressive for a generic CSRF: the network vector and no-privilege metric are consistent with CSRF, but S:C and full C:H/I:H/A:H imply the forged request yields complete compromise, which the one-line description does not substantiate. The UI:R requirement is a meaningful limiter - an authenticated (typically admin) user must be lured into clicking an attacker-controlled link or page, so this is not autonomously wormable. No EPSS value, no KEV listing, and no POC were provided, so real-world exploitation signals are absent; the elevated score reflects theoretical worst-case impact rather than confirmed mass exploitation. CONFLICT TO VERIFY: the vendor's C:H/I:H/A:H and S:C are not supported by any impact detail in the description - treat the true impact as unconfirmed pending vendor advisory review.

Exploit ScenarioDerived

An attacker crafts a web page or email containing a hidden auto-submitting form (or image/script request) targeting a state-changing Avada Core endpoint, then lures a logged-in WordPress administrator to open it. Because the endpoint does not verify an anti-CSRF nonce, the victim's browser submits the forged request with valid session cookies, executing the privileged action under the admin's identity. No public POC is referenced, and the low attack complexity (AC:L) means the forged request itself is trivial to construct once the vulnerable handler is known.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 23, 2026

Cross-Site Request Forgery in the Avada Core (fusion-core) WordPress plugin at versions 5.15.6 and earlier lets a remote attacker forge privileged state-changing requests by tricking an authenticated user into visiting a malicious page. The flaw (CWE-352) carries a vendor/Patchstack CVSS of 9.6 with a scope-changing, high-impact vector and requires victim interaction (UI:R) but no attacker authentication (PR:N). There is no public exploit identified at time of analysis and it is not listed in CISA KEV; no EPSS score was supplied.

RemediationAI

No specific fixed version was provided in the input data - no vendor-released patch version is independently confirmed at time of analysis; consult the Avada vendor/ThemeAdvisor advisory and the Patchstack entry (https://patchstack.com/database/wordpress/plugin/fusion-core/vulnerability/wordpress-avada-core-plugin-5-15-6-cross-site-request-forgery-csrf-vulnerability) and upgrade Avada Core to the first release above 5.15.6 once published. As compensating controls until a patch is applied, deploy a WordPress WAF or Patchstack's virtual patching to block forged cross-origin POSTs, enforce SameSite=Strict/Lax on session cookies to blunt cross-site request delivery (side effect: may break legitimate cross-site integrations), and instruct administrators to log out of wp-admin when browsing untrusted sites and avoid clicking unsolicited links while authenticated. Restricting wp-admin access by IP allowlist further reduces the exposure window at the cost of remote-admin convenience.

Affected VersionsENISA

Avada Core n/a ≤5.15.6

Affected Packages

euvd avada_core no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Avada Core is the companion plugin bundled with the widely-sold Avada WordPress theme, providing shortcodes, portfolio/FAQ post types, and site-building features (the internal/repository slug is 'fusion-core', per the Patchstack reference). The root cause is CWE-352, Cross-Site Request Forgery: one or more privileged action handlers process requests without validating a WordPress nonce or equivalent anti-CSRF token, so the server cannot distinguish a legitimate in-app request from one forged by a third-party site. The single CPE provided, cpe:2.3:a:avada_studio:avada_core:*:*:*:*:*:*:*:*, identifies the affected component but does not enumerate a lower version bound.

Know when Avada Core gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

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

CSRF needs a lured authenticated victim (UI:R, PR:N); the terse description gives no evidence of full compromise or scope change, so I downgrade to S:U with limited C/I impact.

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:P/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
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated Cross Site Request Forgery (CSRF) in Avada Core <= 5.15.6 versions.

Executive ViewAI

Why It Matters

The Avada Core WordPress plugin (fusion-core) versions 5.15.6 and earlier contains a critical cross-site request forgery vulnerability (CVSS 9.6) that allows unauthenticated attackers to manipulate authenticated site administrators into performing unauthorized actions through social engineering. Organizations using this plugin face immediate risk of unauthorized content modification, administrative account compromise, and potential site takeover without requiring any attacker credentials or prior system access.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable the plugin if non-critical to operations; implement WAF rules enforcing CSRF token validation and same-origin checks; restrict admin console access by IP whitelist; enforce multi-factor authentication on all administrative accounts; configure strict Content-Security-Policy and SameSite=Strict cookie attributes; monitor all privileged administrative actions and state-changing requests; prepare rollback or alternative solution for immediate deployment if exploitation is detected.

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Medium
companion plugin of a very popular premium WordPress theme, broad but not universal
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +48
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

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