/

CVE-2026-80099

Severity:

HIGH RISK

(8.8)

Authentication Bypass (CWE-287) in Newfold Plugins

CVE-2026-80099

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Administrator Account Impersonation and Complete Site Takeover

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Several Newfold WordPress plugins contain an authentication bypass in the bundled wp-module-data module. When the expected authentication secret is unavailable, unauthenticated attackers may compute a valid Bearer token and obtain administrator-level access to REST API operations, potentially taking over the site.

Affected context

The vulnerability occurs in Newfold plugins that bundle the affected wp-module-data component, including Crazy Domains, Web, HostGator, and Bluehost integrations. It becomes risky when the module handles unauthenticated REST API requests, the authentication token lookup returns a false value, and the application assigns the first administrator account as the authenticated WordPress user.

Exploit preconditions

  • Attack surface: WordPress REST API endpoints processed by the wp-module-data authentication filter
  • Required access: No prior authentication is generally required
  • Trigger point: Processing of an unauthenticated REST API request containing a Bearer token and timestamp header
  • Required application state: HiiveConnection::get_auth_token() returns false
  • Why exploitation is possible: PHP type coercion reduces the unavailable secret to a predictable value while the remaining token inputs are observable or attacker-controlled, allowing authentication checks to be satisfied without legitimate credentials

Why this happens

The underlying bug is an authentication design failure mapped to CWE-287: Improper Authentication. The authentication routine uses a value returned from a token provider as a cryptographic secret without rejecting failure states, allowing a Boolean false to be coerced into an empty string. This produces a predictable secret component while request-derived values remain controllable, and successful validation then maps the request to an administrator account rather than establishing the identity of a legitimately authenticated user.

Potential impact

  • An attacker may impersonate an administrator through the REST API.
  • An attacker could create additional administrator accounts.
  • An attacker may modify site content, settings, plugins, or users.
  • An attacker could access or alter sensitive WordPress data.
  • A compromised site can be used for malware distribution, spam, or further attacks.

General mitigation guidance

Mitigation generally focuses on making authentication fail closed and ensuring that cryptographic verification depends on a valid, protected secret.

Common defensive patterns include:

  • Rejecting missing, false, empty, malformed, or otherwise invalid token-provider results before authentication calculations.
  • Using well-defined cryptographic verification APIs with strict type checks and constant-time comparisons.
  • Avoiding selection of an administrator account as a fallback identity when the requester's identity has not been independently established.
  • Restricting sensitive REST API operations to explicitly authenticated and authorized principals.
  • Applying least privilege to service accounts and plugin integrations.
  • Reducing exposure of administrative REST endpoints through capability checks, network policy, and centralized access controls.
  • Invalidating potentially exposed sessions, tokens, and administrator credentials as part of incident response.

How teams detect issues like this

Detection can combine code analysis, runtime monitoring, and policy enforcement:

  • Use static analysis rules to identify authentication code that performs cryptographic operations with nullable, Boolean, empty, or unchecked secret values.
  • Review code paths where authentication failures are converted into fallback identities or administrator users.
  • Search for REST authentication filters that process unauthenticated requests and invoke user-context functions without verified identity claims.
  • Monitor REST API requests for unusual administrative actions, administrator creation, privilege changes, and unexpected token or timestamp patterns.
  • Enforce CI policies requiring strict input validation, fail-closed authentication behavior, and explicit authorization checks.
  • Automated security review tools may help identify weak secret handling, unsafe type coercion, and authentication bypass patterns.

Sources

SourceLink
github.comgithub.com/newfold-labs/wp-module-data/commit/9d913fd8fa12796c4d9c09081e4aeccfa5cb1301
github.comgithub.com/newfold-labs/wp-plugin-bluehost/compare/4.19.0...4.19.1
github.comgithub.com/newfold-labs/wp-plugin-crazy-domains/compare/2.5.2...2.5.3
github.comgithub.com/newfold-labs/wp-plugin-hostgator/compare/3.2.0...3.2.1
github.comgithub.com/newfold-labs/wp-plugin-web/compare/2.3.5...2.3.6
plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/wp-module-data/trunk/includes/Data.php#L191
plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/wp-module-data/trunk/includes/Data.php#L201
plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/wp-module-data/trunk/includes/Data.php#L222
plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/wp-module-data/trunk/includes/Data.php#L69
plugins.trac.wordpress.orgplugins.trac.wordpress.org/browser/wp-module-data/trunk/includes/HiiveConnection.php#L406
wordfence.comwordfence.com/threat-intel/vulnerabilities/id/3ee369c0-0d7c-4142-b3ba-a518288647ba?source=cve

Frequently asked

questions

Yes. The affected authentication logic is reached through WordPress REST API requests, and exploitation generally does not require an existing authenticated session when the vulnerable plugin state is present.

No legitimate account is expected to be necessary. The attacker needs network access to an exposed WordPress REST API and a deployment in which the token provider returns the invalid false state.

Authentication should fail closed whenever a secret is missing or invalid. The application should also verify the caller's identity and capabilities independently before allowing administrative REST API operations.

Use strict type and error-state handling for authentication inputs, avoid fallback administrator identities, apply capability checks to every sensitive endpoint, and monitor for unexpected administrative REST activity.

Find out what's already
exploitable in your codebase.