Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11723: CWE-330 Use of Insufficiently Random Values in croixhaug Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin

0
Medium
VulnerabilityCVE-2025-11723cvecve-2025-11723cwe-330
Published: Tue Jan 06 2026 (01/06/2026, 03:21:38 UTC)
Source: CVE Database V5
Vendor/Project: croixhaug
Product: Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin

Description

The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.9.5 via the hash() function due to use of a hardcoded fall-back salt. This makes it possible for unauthenticated attackers to generate a valid token across sites running the plugin that have not manually set a salt in the wp-config.php file and access booking information that will allow them to make modifications.

AI-Powered Analysis

AILast updated: 01/06/2026, 03:54:37 UTC

Technical Analysis

The vulnerability identified as CVE-2025-11723 affects the 'Appointment Booking Calendar — Simply Schedule Appointments Booking' plugin for WordPress, maintained by croixhaug. The root cause is the use of a hardcoded fallback salt in the plugin's implementation of the hash() function, which is intended to generate tokens for securing booking information. This practice violates secure randomness principles (CWE-330), as the fallback salt is predictable and reused across installations that have not explicitly set a unique salt in the wp-config.php configuration file. Consequently, an unauthenticated attacker can replicate the token generation process and produce valid tokens to access sensitive booking data on any vulnerable site. This access can lead to unauthorized viewing and modification of appointment bookings, compromising both confidentiality and integrity. The vulnerability affects all versions up to and including 1.6.9.5. The CVSS 3.1 base score is 6.5 (medium severity), reflecting network attack vector, no privileges required, no user interaction, and partial impact on confidentiality and integrity without affecting availability. No patches or fixes are currently linked, and no exploits have been reported in the wild, but the vulnerability's nature makes it a plausible target for attackers seeking to manipulate appointment data or harvest sensitive client information. The issue underscores the importance of proper cryptographic practices and configuration management in WordPress plugins handling sensitive data.

Potential Impact

For European organizations, especially those in sectors relying heavily on appointment scheduling (healthcare, legal, consulting, education), this vulnerability poses a risk of unauthorized disclosure and manipulation of sensitive client booking information. Exposure of booking details can lead to privacy violations, regulatory non-compliance (e.g., GDPR), reputational damage, and potential operational disruptions if attackers alter appointments. The integrity compromise could result in missed or fraudulent bookings, impacting service delivery and trust. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by attackers scanning for vulnerable WordPress sites. The lack of a patch increases the window of exposure. Organizations using this plugin without a custom salt configured are particularly vulnerable. The impact is heightened in countries with strict data protection laws, where breaches can lead to significant fines and legal consequences.

Mitigation Recommendations

European organizations should immediately verify if the 'Appointment Booking Calendar — Simply Schedule Appointments Booking' plugin is installed and identify the version in use. If affected (version ≤ 1.6.9.5), they should: 1) Configure a unique, strong salt value in the wp-config.php file to override the hardcoded fallback salt, ensuring token generation uses sufficient randomness. 2) Monitor web server logs and application logs for unusual access patterns or token generation attempts. 3) Restrict access to booking management interfaces via IP whitelisting or additional authentication layers where feasible. 4) Regularly back up booking data to detect and recover from unauthorized modifications. 5) Engage with the plugin vendor or community to track the release of official patches or updates addressing this vulnerability. 6) Educate site administrators on secure configuration practices and the risks of default settings. 7) Consider alternative booking plugins with stronger security postures if remediation is delayed. These steps go beyond generic advice by focusing on configuration hardening, monitoring, and layered access controls specific to this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-13T20:37:05.956Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695c838f3839e44175cef8db

Added to database: 1/6/2026, 3:37:51 AM

Last enriched: 1/6/2026, 3:54:37 AM

Last updated: 1/8/2026, 1:01:06 PM

Views: 34

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats