{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3367 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3367 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3367 is a medium-severity cross-site scripting vulnerability in lustmored Lockme calendars integration, published on 11 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3367 and fix it if it is affected.\n\nWhat it is: CVE-2026-3367 is a medium-severity cross-site scripting vulnerability in lustmored Lockme calendars integration, published on 11 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3367 in the wild and no public exploit code.\n\nAffected product: lustmored Lockme calendars integration. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3367/ (Markdown: https://insights.sbomify.com/CVE-2026-3367/index.md)","id":"CVE-2026-3367","markdown":"https://insights.sbomify.com/CVE-2026-3367/index.md","name":"CVE-2026-3367","record":{"aliases":["GHSA-6q4h-2q4c-jmg7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated administrators can inject arbitrary scripts via plugin settings, enabling XSS attacks against other users in WordPress multisite environments.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in Lockme calendars integration","id":"CVE-2026-3367","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":14,"next":{"headline":"Injection Guard \u003c= 1.2.9 - Unauthenticated Stored Cross-Site Scripting via Query Parameter Name","id":"CVE-2026-3368"},"packages":[],"prev":{"headline":"InfoSphere Optim Test Data Fabrication is affected by Arbitrary File Read","id":"CVE-2026-3366"},"products":["Lockme calendars integration"],"published":"2026-07-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["lustmored"]},"summary":"Authenticated administrators can inject arbitrary scripts via plugin settings, enabling XSS attacks against other users in WordPress multisite environments.","url":"https://insights.sbomify.com/CVE-2026-3367/"}