BASEL-POST-TYPES · CVE-2026-89324 · Package
FIX → 1.19
Basel Post Types (XTemos) up to 1.18 has a coding error that makes it always use a hardcoded, publicly visible salt to verify social-login (Opauth) callbacks. An unauthenticated attacker can forge a callback for any existing account, admins included, and get a logged-in session, bypassing passwords and MFA. Fixed in 1.19.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running WordPress with the Basel theme's Post Types plugin at version 1.18 or lower, WooCommerce active, and at least one Basel social-login provider (Facebook, Google or VKontakte) configured. Sites without those settings are not exposed by this description.
Not affected if no-woocommerce, patched-1.19, plugin-not-installed, social-login-not-configured, woocommerce-inactive
Who cares basel-theme, plugin, self-hosted, woocommerce, wordpress, xtemos
Upgrade to 1.19
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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.