On this page (7 sections)

A critical flaw tracked as CVE-2026-89324 affects the Basel Post Types plugin for WordPress, all versions up to and including 1.18. According to the NVD record, an unauthenticated attacker can authenticate as any existing user, including an administrator, bypassing password verification and multi-factor authentication.

If you run a WooCommerce store on the Basel theme and have enabled social login, treat this as urgent. Agencies and hosts that manage Basel-based shops should check their client sites today.

What happened

The CVE was published on 2026-11-10. The record describes a login path that trusts a signature computed with a secret that is not actually secret. Because of a coding mistake, the plugin always falls back to a fixed value that, per the record, is visible in the theme source code. Anyone who knows that value can produce a signature the plugin will accept.

The result, according to the record, is that an attacker can impersonate an existing account by tying a forged callback to its known email address, and the plugin then issues a fully authenticated session cookie. The record also links a Wordfence vulnerability entry and the Basel theme page on ThemeForest. Only one independent publisher covers this story so far, so details beyond the CVE description may still emerge.

Technical details in plain terms

Social login in this plugin works through Opauth, which handles a callback from a provider such as Google and relies on a signature so the site can trust it. The signature depends on a salt. WordPress normally defines a site-unique SECURE_AUTH_SALT in its configuration, and the plugin is supposed to use it.

According to the CVE record, the defined() check for that constant in BASEL_Auth::get_config() is written without quotes around the constant name. PHP therefore evaluates the constant's value instead of testing whether the name exists, so the check always fails. The plugin then permanently falls back to a static, hardcoded salt.

This is a classic case of authentication built on a shared, known secret. Once the secret is public, the signature proves nothing. The record says the forged callback is submitted to an unauthenticated init hook endpoint and processed by register_or_login, so no prior login is required. It also says this bypasses password verification, multi-factor authentication and ownership checks.

This article deliberately leaves out the salt value and any forging details. They are not needed to defend a site.

Who is affected

Exposure is narrower than the version range suggests. The record states that exploitation requires both of these conditions:

  • WooCommerce is active on the site.
  • 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 running Basel Post Types 1.18 or earlier without social login configured do not meet the stated conditions, but they still run an affected version and should not rely on that alone. The record does not say whether later versions are fixed, so confirm that with the vendor.

How to check your exposure

First, find out whether the plugin is installed and which version it is. This read-only WP-CLI command lists installed plugins with their status and version; look for a basel-related entry and compare its version with 1.18.

List plugins and versions (run from the WordPress root as a user that can run WP-CLI)WP-CLI
wp plugin list --fields=name,status,version

If you do not have shell access, open Plugins in the WordPress admin and read the version under Basel Post Types. Then check the theme's settings for social login: if Facebook, Google or VKontakte entries contain an app ID and secret, the second condition is likely met.

Next, look for signs that someone already used the flaw. The record does not describe log indicators, so these are general checks:

  • Review administrator and shop-manager accounts for any you do not recognize, and check recent changes to roles.
  • Look in access logs for requests with an opauth query parameter from unfamiliar IP addresses, followed by admin activity.
  • Check recent plugin, theme and user changes, and recently modified files.

This read-only command searches web server access logs for requests containing opauth. Adjust the log paths for your server; matching lines are requests to review.

Search web server access logs for requests containing opauth (adjust the log path for your server)Shell
grep -i "opauth" /var/log/nginx/access.log* /var/log/apache2/access.log* 2>/dev/null

Legitimate social logins will also appear, so look for patterns such as many attempts, unknown IPs, or an admin session starting right after one. Our guide on checking whether a website is hacked covers wider signs of compromise.

What to do now

The research does not name a patched version and gives no vendor mitigation. The steps below are our own suggestions, derived from the exploitation conditions in the CVE record. They are not vendor guidance.

  1. Identify every site running Basel Post Types and note its version.
  2. Check the vendor's channel (the ThemeForest listing) for an update newer than 1.18, and install it once available after reading its notes.
  3. Suggested workaround (our inference, not vendor guidance): until a fix is confirmed, disable social login by removing the Facebook, Google and VKontakte app_id and app_secret values in the Basel theme settings. The record lists a configured provider as a condition for exploitation, so this should remove that condition, but it is not verified by the sources.
  4. If you cannot confirm that social login is off or the plugin is fixed, consider deactivating the plugin or putting the shop in maintenance mode, after weighing the impact on customers.
  5. Review all administrator and shop-manager accounts and remove any that are unexpected.
  6. If you see signs of misuse, reset passwords for privileged users and invalidate existing sessions. Rotating the social provider app secrets is a reasonable precaution in that case (our suggestion).
  7. Take a backup before changes, and review recently modified files and installed plugins for anything you did not add.
Caution. Deactivating a plugin or clearing theme settings can break login and checkout features on a live store. Test on staging if you can, and make a backup first.
Tip. Rotating the WordPress salts in wp-config.php logs out all users, which can help after a suspected account takeover. Our inference: because the CVE description says the plugin falls back to a static salt, rotating the site's salts is not expected to address this flaw itself.

Detection and monitoring afterwards

Authentication bypasses leave little trace in the login form, because the attacker never submits a password. Watch for new administrator accounts, unexpected plugin or theme installs, and changes to files. A web application firewall can add a layer of filtering for suspicious requests, but it is not a substitute for removing the vulnerable path.

For ongoing visibility, Webforta Monitor can watch uptime, certificate, DNS and header changes, and the WordPress security checklist lists hardening steps such as limiting admin accounts and enforcing least privilege. You can also look up known issues per plugin on our WordPress plugin vulnerabilities page.

What we do not know yet

  • A fixed version has not been stated in the research.
  • Exploitation status is unconfirmed: the sources do not report active exploitation, and the research contains no CISA KEV entry for this CVE.
  • Coverage is limited to the NVD record and one linked vulnerability entry, so treat details as provisional and recheck the vendor and Wordfence pages for updates.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-89324: The Basel Post Types plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.18.nvd.nist.gov ·
  • WordPress
  • CVE-2026-89324
  • Basel
  • WooCommerce
  • Authentication bypass