XTemos
Not on CISA's list of exploited flaws, and not in the news we track.
CVE-2026-89324Critical9.8
Chance of exploitation in the next 30 days
0.70%
EPSS score from FIRST
Reading the vendor advisory
Black Shard's team can check your exposure to CVE-2026-89324 and take the fix off your plate.
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.
Updated 13 Nov 2026, 11:05 UTC, 33 of 36 sources answering.
Black Shard's team can check your exposure, take a fix off your plate or step in on a live incident.