LiveActive security incident?Get immediate response
CVE Record

CVE-2023-39311: WordPress Avada Builder plugin <= 3.11.1 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in ThemeFusion Fusion Builder.This issue affects Fusion Builder: from n/a through 3.11.1.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in ThemeFusion Fusion Builder, also referenced as WordPress Avada Builder, through version 3.11.1. A logged-in user could be tricked into causing unwanted site changes. The source bundle rates it high, mainly because availability impact is high. No provided source confirms active exploitation.

Executive priority

Treat this as a high-priority WordPress plugin hygiene issue for affected sites, especially business-critical public sites. It is not proven exploited from the provided evidence, but CSRF against privileged users can still create operational disruption.

Technical view

CWE-352 CSRF affects the fusion-builder package through 3.11.1. CVSS 3.1 is 7.1: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H. The issue requires user interaction and has no stated confidentiality impact, low integrity impact, and high availability impact. Sources do not provide vulnerable endpoint details or remediation text.

Likely exposure

Exposure is most likely on WordPress sites running ThemeFusion Fusion Builder or Avada Builder version 3.11.1 or earlier. The bundle does not identify affected CPEs, hosting platforms, or whether bundled theme installations differ from standalone plugin installations.

Exploitation context

The CVE is not marked as CISA KEV, and the supplied sources do not claim active exploitation. Practical risk depends on whether an attacker can lure an authenticated WordPress user, likely an administrator or editor, into triggering a forged request.

Researcher notes

The source bundle is sparse: it identifies CWE, affected version range, CVSS, and Patchstack reference, but not vulnerable actions, nonce behavior, proof of concept, or fixed version. Avoid assuming exploitability beyond authenticated-user CSRF risk until vendor details are reviewed.

Mitigation direction

  • Inventory WordPress sites for Fusion Builder or Avada Builder versions through 3.11.1.
  • Check ThemeFusion and Patchstack guidance for the vendor-supported fixed version or mitigation.
  • Prioritize administrator awareness for suspicious links while remediation is pending.
  • Limit privileged WordPress accounts to users who currently need access.
  • Review WAF or security plugin protections without treating them as a patch.

Validation and detection

  • Confirm installed Fusion Builder or Avada Builder version on each WordPress site.
  • Check whether affected sites are internet-facing and have active privileged users.
  • Review WordPress audit logs for unexpected builder or settings changes.
  • Verify remediation status against vendor or Patchstack advisory text.
  • Document sites where evidence is incomplete or version data is unavailable.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-39311 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-39311Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeFusionFusion Builderfusion-builder, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.