Critical

CVE-2026-89324: Basel Post Types WordPress Auth Bypass

Inttelio Threat Feeds ·

The Basel Post Types plugin for WordPress, used with the Basel ecommerce theme, has a critical authentication bypass (CVSS 9.8) in all versions up to and including 1.18. A coding error makes the plugin always fall back to a hardcoded salt that is publicly visible in the theme source code. An unauthenticated attacker can use that salt to forge a social-login callback and get a fully authenticated session as any existing user, including administrators.

CVECVE-2026-89324
CVSS v3.19.8 CRITICAL
WeaknessCWE-287
Exploited in the wildNot listed in CISA KEV
PublishedNovember 10, 2026

Who is affected

WordPress sites running the Basel Post Types plugin version 1.18 or earlier, which ships with the Basel Responsive eCommerce Theme. According to the source data, a site is exploitable only when both of these are true: WooCommerce is active, and at least one Basel social-login provider (Facebook, Google, or VKontakte) is configured with a valid app_id and app_secret in the theme settings. Sites with the plugin installed but no social-login provider configured do not meet the stated exploitation conditions. However, they still run vulnerable code and should be updated. The source data does not name a fixed version.

What attackers can do

An attacker needs no account and no user interaction. The flaw is in BASEL_Auth::get_config(). Because quotes are missing in a defined() check, the check for the site's SECURE_AUTH_SALT always fails, and the plugin uses a static, publicly known salt instead. With that salt, an attacker can compute a valid Opauth signature offline. They then send a forged ?opauth callback to an unauthenticated endpoint handled by register_or_login. If the callback is tied to a target account's email address, the attacker receives an authenticated session cookie for that account. This skips password checks, multi-factor authentication, and ownership checks. If the target is an administrator, the attacker gets full control of the site. On a WooCommerce store, that can include access to customer and order data, changes to the site, and planting malicious code. The vulnerability is rated high impact for confidentiality, integrity, and availability.

Exploitation status

The source data contains no CISA Known Exploited Vulnerabilities (KEV) entry, so there is no confirmed report here of exploitation in the wild. Treat this as high risk anyway. The flaw is unauthenticated and network-reachable, the salt needed to exploit it is public, and the description gives enough detail to make exploitation straightforward.

What to do now

  1. Inventory your WordPress sites for the Basel theme and the Basel Post Types plugin, and record the plugin version. Any version 1.18 or earlier is vulnerable.
  2. Update the Basel Post Types plugin and theme to a release that fixes CVE-2026-89324. The source data does not state a fixed version, so check the Wordfence advisory and the vendor's ThemeForest page to confirm which version contains the fix.
  3. If you cannot update right away, disable Basel social login. Remove the Facebook, Google, and VKontakte app_id and app_secret values from the theme settings. Per the source data, at least one configured provider is required for exploitation. Deactivating the plugin until a fix is applied also removes the vulnerable code.
  4. Check for signs of compromise. Look for unexpected administrator or other user sessions and logins, especially any made through ?opauth callback requests in web server logs. Look for newly created or modified admin accounts, unfamiliar plugins or themes, changed files, and unexpected changes to WooCommerce settings or orders.
  5. If you find suspicious activity, take these steps. Force logout of all sessions and rotate passwords for administrator accounts. Regenerate the WordPress salts and keys in wp-config.php. Rotate the social-login app secrets with each provider. Then follow your incident response process, including any customer notification obligations for exposed data.
  6. Add this plugin to your ongoing patch monitoring. Premium theme bundles often update outside the normal WordPress.org update channel.

Frequently asked questions

Which versions of Basel Post Types are affected by CVE-2026-89324?

All versions up to and including 1.18 are affected. The source data does not name a fixed version. Check the Wordfence advisory or the Basel theme's ThemeForest page for the patched release.

Is my Basel site exploitable if I don't use social login?

According to the source data, exploitation requires two things: WooCommerce must be active, and at least one Basel social-login provider (Facebook, Google, or VKontakte) must be configured with a valid app_id and app_secret. Without a configured provider, the stated conditions are not met. You should still update, because the vulnerable code remains on the site.

Is CVE-2026-89324 being exploited in the wild?

The source data contains no CISA KEV entry, so exploitation in the wild is not confirmed here. The flaw needs no authentication and relies on a publicly known hardcoded salt, so it should be treated as urgent.

Sources

This briefing was drafted with AI from the official NVD and CISA records. Always confirm affected versions and fixes in the vendor advisory.

Not sure if you are exposed?

Our penetration testers find exploitable flaws before attackers do, and a vCISO can run your vulnerability program.

Talk to Inttelio