Avada - Cross-Site Request Forgery (CSRF) (CVE-2017-18607)
CVE-2017-18607
The avada theme before 5.1.5 for WordPress has CSRF.
CVE-2017-18607
CVE-2017-18607
The avada theme before 5.1.5 for WordPress has CSRF.
CVE-2017-18607
Machine-generated threat intelligence
AI Updated 3 days ago
AI enriched 3 days ago (2026-09-15 23:55 UTC)
The avada theme before 5.1.5 for WordPress has CSRF.
Severity is HIGH (CVSS 8.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability is assessed as High based on severity and technical exposure profile.
Primary risk drivers: severity and technical exposure profile
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
AI risk score 78/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.
Patch on your next cycle Worth fixing, but not ahead of other work.
Update Avada to 5.1.5 or later.
That is the complete fix. Everything below is what protects you in the meantime.
Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.
Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.
Scan your site to see whether it runs Avada, and at which version.
Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.
You are affected if your site runs Avada. Versions below 5.1.5 are vulnerable; that release and later are not.
Update Avada to version 5.1.5 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.
This is a Cross-Site Request Forgery (CSRF) flaw. An attacker who exploits it can make a logged-in administrator perform an action just by visiting a page.