LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47781: WordPress Thrive Theme Builder Theme < 3.24.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Thrive Themes Thrive Theme Builder < 3.24.2 versions.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects WordPress sites running Thrive Theme Builder before 3.24.2. A malicious site could potentially trick a logged-in site administrator into performing unintended actions, with reported impact up to account takeover. Business risk is highest for public WordPress sites where administrators browse while authenticated.

Executive priority

Treat this as high priority for WordPress sites using Thrive Theme Builder, especially customer-facing or revenue-supporting sites. Patch quickly, but do not assume compromise without supporting evidence.

Technical view

CVE-2023-47781 is a CSRF vulnerability in Thrive Themes Thrive Theme Builder versions before 3.24.2. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no attacker privileges, and required user interaction. The source bundle identifies CWE-352 and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress installations using Thrive Theme Builder below 3.24.2. The provided data does not identify other Thrive products, specific endpoints, or hosting environments as affected.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source establishes active exploitation. Practical abuse requires user interaction, likely involving a logged-in WordPress user being induced to trigger an unintended authenticated action.

Researcher notes

Available sources identify the vulnerability class, product, severity, and affected version boundary, but do not provide endpoint-level details or proof of active exploitation. Avoid extrapolating to other Thrive plugins unless vendor guidance confirms it.

Mitigation direction

  • Inventory WordPress sites using Thrive Theme Builder.
  • Update Thrive Theme Builder to version 3.24.2 or later.
  • Check Thrive Themes and Patchstack guidance for any additional remediation.
  • Reduce administrator browsing exposure while logged into WordPress.
  • Review recent administrator account and theme configuration changes.

Validation and detection

  • Confirm installed Thrive Theme Builder versions across WordPress assets.
  • Flag any instance below 3.24.2 as vulnerable.
  • Verify update completion through WordPress admin or asset inventory.
  • Review logs for unexpected account or theme-setting changes.
  • For code review, confirm sensitive actions use CSRF protection and capability checks.
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-47781 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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
Thrive ThemesThrive Theme Buildern/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.