CVE Vulnerabilities


Missing Authentication for Critical Function

Published: Apr 12, 2021 | Modified: Jul 29, 2022
CVSS 3.x
CVSS 2.x

The Thrive Optimize WordPress plugin before, Thrive Comments WordPress plugin before, Thrive Headline Optimizer WordPress plugin before, Thrive Leads WordPress plugin before, Thrive Ultimatum WordPress plugin before, Thrive Quiz Builder WordPress plugin before, Thrive Apprentice WordPress plugin before, Thrive Visual Editor WordPress plugin before, Thrive Dashboard WordPress plugin before, Thrive Ovation WordPress plugin before 2.4.5, Thrive Clever Widgets WordPress plugin before 1.57.1 and Rise by Thrive Themes WordPress theme before 2.0.0, Ignition by Thrive Themes WordPress theme before 2.0.0, Luxe by Thrive Themes WordPress theme before 2.0.0, FocusBlog by Thrive Themes WordPress theme before 2.0.0, Minus by Thrive Themes WordPress theme before 2.0.0, Squared by Thrive Themes WordPress theme before 2.0.0, Voice WordPress theme before 2.0.0, Performag by Thrive Themes WordPress theme before 2.0.0, Pressive by Thrive Themes WordPress theme before 2.0.0, Storied by Thrive Themes WordPress theme before 2.0.0, Thrive Themes Builder WordPress theme before 2.2.4 register a REST API endpoint associated with Zapier functionality. While this endpoint was intended to require an API key in order to access, it was possible to access it by supplying an empty api_key parameter in vulnerable versions if Zapier was not enabled. Attackers could use this endpoint to add arbitrary data to a predefined option in the wp_options table.


The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Affected Software

Name Vendor Start Version End Version
Focusblog Thrivethemes * 2.0.0 (excluding)
Ignition Thrivethemes * 2.0.0 (excluding)
Luxe Thrivethemes * 2.0.0 (excluding)
Minus Thrivethemes * 2.0.0 (excluding)
Performag Thrivethemes * 2.0.0 (excluding)
Pressive Thrivethemes * 2.0.0 (excluding)
Rise Thrivethemes * 2.0.0 (excluding)
Squared Thrivethemes * 2.0.0 (excluding)
Storied Thrivethemes * 2.0.0 (excluding)
Thrive_apprentice Thrivethemes * (excluding)
Thrive_clever_widgets Thrivethemes * 1.57.1 (excluding)
Thrive_comments Thrivethemes * (excluding)
Thrive_dashboard Thrivethemes * (excluding)
Thrive_headline_optimizer Thrivethemes * (excluding)
Thrive_optimize Thrivethemes * (excluding)
Thrive_ovation Thrivethemes * 2.4.5 (excluding)
Thrive_quiz_builder Thrivethemes * (excluding)
Thrive_themes_builder Thrivethemes * 2.2.4 (excluding)
Thrive_visual_editor Thrivethemes * (excluding)
Voice Thrivethemes * 2.0.0 (excluding)

Extended Description

As data is migrated to the cloud, if access does not require authentication, it can be easier for attackers to access the data from anywhere on the Internet.

Potential Mitigations

  • Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
  • Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port.
  • In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
  • Where possible, avoid implementing custom authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These may make it easier to provide a clear separation between authentication tasks and authorization tasks.
  • In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].