External risk intelligence

Basel Post Types WordPress Plugin Authentication Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-89324

The vulnerability affects a WordPress plugin used for e-commerce, specifically requiring WooCommerce and social login features to be active. These components are commonly deployed on public-facing websites to facilitate user authentication and shopping functionality, making the vulnerable endpoint reachable from the internet as part of the standard web application interface.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability in a WordPress plugin could allow unauthenticated attackers to bypass security measures and gain administrative access to websites. The issue stems from a coding error that exposes a hardcoded security key, enabling attackers to forge login credentials without needing passwords or multi-factor authentication, provided specific e-commerce and social login configurations are active.

  • Allows attackers to bypass logins.
  • Critical for e-commerce sites with social logins.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can bypass authentication by exploiting a coding error in the Basel Post Types plugin. This allows them to forge a valid signature and impersonate any user, including administrators, by submitting a crafted callback. Exploitation requires WooCommerce and a configured social login provider.

  • Unauthenticated network access to a website.
  • Forged social login callback to vulnerable endpoint.
  • Full user account takeover.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to bypass authentication mechanisms on WordPress sites. Exploitation requires WooCommerce to be active and at least one Basel social-login provider to be configured. When these conditions are met, an attacker could impersonate any existing WordPress user, including administrators, by forging a callback that grants them an authenticated session cookie.

  • WordPress user accounts and administrator access.
  • Forging a callback to register_or_login endpoint.
  • Unauthenticated takeover of user accounts.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability impacts the Basel Post Types plugin for WordPress, specifically when used with WooCommerce and configured social login providers. The primary responsibility for addressing this likely falls to the Application Owners or Web Development Teams who manage the WordPress instance, in coordination with Infrastructure Teams responsible for the hosting environment. The first practical step is to identify all WordPress sites using this plugin, determine if WooCommerce and social logins are active, confirm the specific versions in use, and then prioritize remediation based on exposure and business criticality.

  • Application owners should verify plugin usage.
  • Confirm WooCommerce and social logins are active.
  • Plan coordinated plugin updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Basel Post Types plugin for WordPress?

The Basel Post Types plugin is a component of the Basel responsive e-commerce theme. It provides specific functionality for managing content types and integrates with WooCommerce to enable features like social media login—such as Facebook, Google, or VKontakte—to streamline the customer checkout and registration process on WordPress-based online stores.

How does CVE-2026-89324 allow authentication bypass?

This vulnerability involves Improper Authentication (CWE-287). A coding error in how the plugin handles security salts causes it to fall back on a static, hardcoded value that is visible in the theme's source code. Because this salt is known, an attacker can mathematically compute a valid login signature offline and submit it to the plugin to impersonate any user, effectively tricking the system into granting an authenticated session without a password.

Do I need WooCommerce active for this to be a risk?

Yes. The vulnerability is not triggered if WooCommerce is inactive. Additionally, the flaw relies on the Basel theme's social login features being enabled and configured with valid application credentials. If you do not use the social login functionality or have these specific provider settings turned off, the vulnerable code path that processes the forged callback is not reachable.

Is my site at risk according to Halo Surface Signal?

Halo Surface Signal identifies this as a likely risk because the plugin is designed for e-commerce, which is typically hosted on public-facing websites. Since the vulnerable endpoint is exposed to the internet to support standard user registration and shopping features, any WordPress site using this plugin with the required configurations is potentially reachable by an external attacker.

What should I do if I run this technology?

First, inventory your WordPress sites to identify which instances are using the Basel Post Types plugin. Next, confirm if WooCommerce is installed and if any social login providers are active. If these components are present, prioritize these sites for updates or removal of the vulnerable plugin, and coordinate with your web development team to ensure the authentication mechanism is secured.

References