The Lockme OAuth2 calendars integration plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'App ID' setting in all versions up to, and including, 2.11.0. This is due to insufficient input sanitization and output escaping. The register_setting() call on line 197 lacks a sanitize callback, allowing unsanitized data to be stored via update_option(). When the settings page is rendered, the stored value is echoed directly into an HTML input's value attribute without esc_attr() on line 212. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in the settings page that will execute whenever a user accesses the plugin settings page. Multiple fields are affected: App ID (client_id), App Secret (client_secret), Bookings ID prefix (id_prefix), and API domain (api_domain). This vulnerability is particularly impactful in WordPress multisite installations where administrators of individual sites should not be able to execute JavaScript affecting other users.
Metrics
Affected Vendors & Products
References
History
Mon, 13 Jul 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 13 Jul 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lustmored
Lustmored lockme Calendars Integration Wordpress Wordpress wordpress |
|
| Vendors & Products |
Lustmored
Lustmored lockme Calendars Integration Wordpress Wordpress wordpress |
Sat, 11 Jul 2026 03:30:00 +0000
Status: PUBLISHED
Assigner: Wordfence
Published: 2026-07-11T02:31:17.819Z
Updated: 2026-07-13T14:26:53.516Z
Reserved: 2026-02-27T20:56:31.267Z
Link: CVE-2026-3367
Updated: 2026-07-13T14:26:49.343Z
No data.
No data.