← Back to search

CVE-2026-89324

9.8 CRITICAL

Published 2026-11-10 · Updated 2026-11-10

AI risk analysis

Summary
The Basel Post Types WordPress plugin (≤1.18) contains a missing-quotes bug in a PHP `defined()` call for `SECURE_AUTH_SALT`, causing authentication bypass via a hardcoded, publicly exposed salt value. This allows unauthenticated attackers to forge valid Opauth callbacks and authenticate as any user—including admins—without credentials or MFA.
Exploitability
Exploitation requires WooCommerce to be active and at least one Basel social-login provider (Facebook, Google, or VKontakte) configured with valid app credentials, but otherwise is trivial for remote attackers with no authentication.
Blast radius
Successful exploitation grants full administrative access to the WordPress site, enabling complete compromise of data, users, and infrastructure.
Detection
Defenders should monitor for unauthenticated POST requests to the Opauth callback endpoint (e.g., `/index.php?opauth`) containing forged signature parameters, especially when paired with `wc_set_customer_auth_cookie()` in server logs or application logs indicating session creation for unknown or high-privilege users without prior login attempts.
Prioritized remediation
Upgrade to Basel Post Types plugin version 1.19 or later; if unavailable, disable social login functionality and restrict access to the `/wp-login.php` and Opauth callback endpoints until patched.
auth-bypasswordpresssocial-loginhardcoded-secretwoocommerce

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.

NVD description

The Basel Post Types plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.18. The vulnerability exists because a missing-quotes coding error in the defined() call for SECURE_AUTH_SALT inside BASEL_Auth::get_config() causes PHP to evaluate the constant's value rather than its name, making the check always fail and permanently falling back to the static hardcoded salt 2NlBUibcszrVtNmDnxqDbwCOpLWq91eatIz6O1O that is publicly visible in the theme source code; because this salt is static and known, an attacker can compute a valid Opauth signature entirely offline and submit a forged ?opauth callback to the unauthenticated init hook endpoint processed by register_or_login. This makes it possible for unauthenticated attackers to authenticate as any existing WordPress user, including administrators, by forging a callback tied to a known target account email address — bypassing all password verification, multi-factor authentication, and ownership checks, and receiving a fully authenticated session cookie via wc_set_customer_auth_cookie(). Exploitation requires WooCommerce to be active and at least one Basel social-login provider (Facebook, Google, or VKontakte) to be configured with a valid app_id and app_secret in the theme settings.

CVSS vector

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

Weaknesses

CWE-287

All references

Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.

Related CVEs

Related by shared AI tags and CWE weakness class. Browse the full archive.