dbcve.org
Thrive AutomatorWordPress extension · Thrivethemes

CVE-2023-51531

HIGH · 8.8 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 1.17.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Thrive Themes Thrive Automator.This issue affects Thrive Automator: from n/a through 1.17.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in Thrive Automator WordPress plugin allows attackers to trick authenticated users into performing unintended actions by leveraging the lack of proper nonce validation on sensitive operations.

MitigationUpdate Thrive Automator to the latest version when available; the fix requires implementing anti-CSRF nonce tokens on all state-changing actions and form submissions within the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Thrive AutomatorWordPress extension
Affected:< 1.17.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Thrive Automator is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Thrive Automator' by Thrive Themes. Note whether it is installed and activated.
    Affected if The plugin is installed and activated on the WordPress site
  2. Check installed version number
    On the Plugins page, find Thrive Automator and note the version number displayed. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The version number is lower than 1.17.1 (e.g., 1.17.0, 1.16.2, etc.)
  3. Inspect nonce validation in plugin code
    Using a file manager or FTP, navigate to wp-content/plugins/thrive-automator. Examine PHP files handling form submissions and state-changing actions (typically in action-hooks or admin pages). Look for wp_verify_nonce or check_admin_referer calls before performing sensitive operations.
    Affected if Sensitive action handlers lack nonce verification or use it inconsistently across different endpoints
  4. Review action hooks for CSRF protection
    Examine the plugin's register_action() or similar action registration files. Check if nonce fields are required in frontend forms or AJAX handlers that trigger automated workflows.
    Affected if Forms and AJAX endpoints that modify workflow data do not require nonce token submission or server-side validation

A user is affected if Thrive Automator is installed with a version lower than 1.17.1 and the plugin's sensitive operations lack proper nonce validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.17.1 or later
Fixed in 1.17.1
Interim mitigation

Update Thrive Automator to the latest version when available; the fix requires implementing anti-CSRF nonce tokens on all state-changing actions and form submissions within the plugin.

Recommended fix High confidence

Thrive Automator 1.17.1 or later

  1. Log in to the WordPress admin dashboard where Thrive Automator is installed
  2. Navigate to Plugins section
  3. Find Thrive Automator in the installed plugins list
  4. Check if an update to version 1.17.1 or later is available
  5. If update available, click Update Now to upgrade to the fixed version
  6. If automatic updates are not configured, manually download Thrive Automator 1.17.1 or later from the Thrive Themes portal and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version is 1.17.1 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Thrive Automator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51531 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51531 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data