Read the docs

Authentication bypass in Basel Post Types allows login as any user

Priority MEDIUM 44CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

The XTemos Basel Post Types plugin for WordPress through 1.18 has an improper authentication flaw (CWE-287). A coding error makes it always fall back to a hardcoded salt visible in the theme source. An unauthenticated remote attacker can forge a login callback with that salt and log in as any existing user, including administrators. WooCommerce and a configured social login provider are required.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00704 53rd percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
xtemosBasel Post Typesup to 1.18—No fix listedCNA
  • Basel Post Types Vendorxtemos Affected up to 1.18 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Basel Post Types.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-89324
  2. 2026-11-11 Alias added: GHSA-954p-gvc3-xfxg
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2023-15542 WordPress Woodmart Core plugin <= 1.0.36 - Privilege Escalation CVSS 3.1CRITICAL 9.8
  • TI-2023-15540 WordPress Woodmart Core Plugin <= 1.0.36 is vulnerable to PHP Object Injection CVSS 3.1CRITICAL 9.8
  • TI-2025-06127 WoodMart <= 8.2.3 - Authenticated (Contributor+) Local File Inclusion CVSS 3.1HIGH 8.8
  • TI-2023-15782 WordPress WoodMart Theme <= 7.1.1 is vulnerable to Cross Site Request Forgery (CSRF) CVSS 3.1HIGH 8.8
  • TI-2025-06125 Woodmart <= 8.2.3 - Unauthenticated Arbitrary Shortcode Execution CVSS 3.1HIGH 7.3
  • TI-2026-28556 WordPress Hitek theme < 1.8.3 - Local File Inclusion vulnerability CVSS 3.1HIGH 8.1
See all 22 →

Sources