Live › vulnerability › CVE-2026-104000
Go to dashboardThe Simply Schedule Appointments WordPress plugin up to and including 1.6.12.35 fails to sanitize the 'status' parameter, so unauthenticated attackers can store scripts that run in visitors' browsers. Because debug logging is on by default, the payload can reach an administrator's session when they view the debug log during support work.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Simply Schedule Appointments WordPress plugin at version 1.6.12.35 or earlier are exposed, especially where debug logging is enabled, which is the default. Sites that do not run the plugin can skip it. Sites that have the plugin but have upgraded past 1.6.12.35 are not affected.
No product ranges from the sources yet.
wp plugin get simply-schedule-appointments --field=version with WP-CLI1.6.12.35Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Simply Schedule Appointments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'status' parameter in all versions up to, and including, 1.6.12.35 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The malicious payload is stored unconditionally because debug logging is enabled by default, and the debug-log viewer is accessible to anyone holding the site-wide Support PIN (an HMAC-MD5 of AUTH_SALT displayed in wp-admin), meaning the injected script will execute against the administrator's session during ordinary support or troubleshooting workflows.
This page as .md · .json · in your agent: get_signal("CVE-2026-104000")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.