CVE-2026-3367

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreHIGH confidence

Score 4.4 from GitHub Security Advisory published 2026-07-11. a secondary CVSS source baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.4
EG Score
4.4(high)
EPSS
17.0%
KEV
Not listed

Published

July 11, 2026

Last Modified

July 13, 2026

References (14)

Vendor Advisories for CVE-2026-3367(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 00:32 UTCEG score recompute
  2. 2026-07-16 00:32 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 01:07 UTCEG score recompute
  7. 2026-07-15 01:07 UTCGHSA enrichment
  8. 2026-07-14 01:43 UTCEG score recompute
  9. 2026-07-14 01:42 UTCGHSA enrichment
  10. 2026-07-13 22:30 UTCEPSS rescore
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 02:17 UTCEG score recompute
  14. 2026-07-13 02:17 UTCGHSA enrichment
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 02:53 UTCEG score recompute
  17. 2026-07-12 02:53 UTCGHSA enrichment
  18. 2026-07-11 03:28 UTCEG score recompute
  19. 2026-07-11 03:27 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-3367?
CVE-2026-3367 is a medium vulnerability published on July 11, 2026. 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 registersetting() call on line 197 lacks a…
When was CVE-2026-3367 disclosed?
CVE-2026-3367 was first published in the National Vulnerability Database on July 11, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3367 actively exploited?
CVE-2026-3367 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-3367?
CVE-2026-3367 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-3367?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3367, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3367

Explore →

Is Your Infrastructure Affected by CVE-2026-3367?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs