lustmored Lockme calendars integration Plugin up to 2.11.0 on WordPress Plugin Settings register_setting/update_option client_id/client_secret/id_prefix/api_domain cross site scripting

Summaryinfo

A vulnerability, which was classified as problematic, has been found in lustmored Lockme calendars integration Plugin up to 2.11.0. The affected element is the function register_setting/update_option of the component Plugin Settings. The manipulation of the argument client_id/client_secret/id_prefix/api_domain leads to cross site scripting. This vulnerability is referenced as CVE-2026-3367. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in lustmored Lockme calendars integration Plugin up to 2.11.0 and classified as problematic. This issue affects the function register_setting/update_option of the component Plugin Settings. The manipulation of the argument client_id/client_secret/id_prefix/api_domain with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

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.

It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-3367 since 02/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• lustmored

Name

• Lockme calendars integration Plugin

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion