WordPress plugin
Lockme calendars integration security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 1 known vulnerability is fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High0
- Medium1
- Low0
All Lockme calendars integration vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.4 | Authenticated (Administrator+) Stored Cross-Site Scripting via 'App ID' Setting ≤2.11.0Update to 2.11.1 | CVE-2026-3367 |
- Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting via 'App ID' Setting
≤2.11.0Update to 2.11.1
Lockme calendars integration: common questions
Does Lockme calendars integration have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Lockme calendars integration: 1 medium. None are known to affect version null.
How do I check which version of Lockme calendars integration I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Lockme calendars integration vulnerability?
CVE-2026-3367, published Jul 10, 2026: Lockme OAuth2 calendars integration <= 2.11.0 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'App ID' Setting. Severity: Medium (CVSS 4.4).
Is any Lockme calendars integration vulnerability listed in CISA KEV?
No. None of the known Lockme calendars integration vulnerabilities is currently listed in the CISA KEV catalog.