Basel Post Types - Security Vulnerability (CVE-2026-89324)

Q: Am I affected by this vulnerability?

You are affected if your site runs Basel Post Types. No account is needed to exploit this, so a public site is reachable by anyone.

Q: How do I fix it?

Update Basel Post Types to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Administrator multi-factor authentication in Hack Halt Pro contains this class of attack at the request layer.

Q: What can an attacker actually do?

This is a Authentication Bypass flaw. An attacker who exploits it can sign in as another user, frequently an administrator, without a password.

CVE-2026-89324

Vulnerability CVE-2026-89324 PLUGIN basel-post-types CRITICAL

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.

CVE-2026-89324

CRITICAL CVSS 9.8 Published 2026-11-10 Updated 2026-11-10

AI Risk Critical (100/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P1 Immediate

Severity Band CRITICAL

CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected Components 1

Reference Links 2

AI Risk Engine Critical (100/100)

Exploitability Very High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-11-10 CVE published and first recorded in the threat feed.
2026-11-10 Record updated with latest vulnerability metadata.
2026-11-13 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 8 hours ago

AI enriched 8 hours ago (2026-11-13 18:41 UTC)

Technical Summary

Potential Impact

Severity is CRITICAL (CVSS 9.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Very High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 100/100 (Critical, Very High) with priority P1 Immediate. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Basel Post Types PLUGIN · basel-post-types Affected: <= 1.18 Fixed version not specified

References

What to do about this

Patch immediately Serious, and reachable without meaningful privilege.

Fix it

Update Basel Post Types to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Administrator multi-factor authentication in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Require a second factor for every administrator account. This is the single highest-value control against credential stuffing and reused passwords, because a valid password alone stops being enough.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Basel Post Types, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?