Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost malicious CSRF page
-
DeliveryLure authenticated admin to visit
-
ExploitBrowser submits forged request with cookies
-
ExecutionMissing nonce check accepts request
-
ImpactPrivileged 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Request Forgery (CSRF) in Avada Core <= 5.15.6 versions.
Executive ViewAI
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
More in Avada Core
View allA DOM-based Cross-Site Scripting (XSS) vulnerability exists in ThemeFusion Avada Core plugin versions prior to 5.15.0, a
This is a missing authorization vulnerability in ThemeFusion Avada Core (versions prior to 5.15.0) that allows unauthent
EUVD-2026-48083
GHSA-92mf-w334-37r6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB