{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9722 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9722 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9722 is a medium-severity vulnerability in pcis Laiser Tag, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-9722 and fix it if it is affected.\n\nWhat it is: CVE-2026-9722 is a medium-severity vulnerability in pcis Laiser Tag, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-9722 in the wild and no public exploit code.\n\nAffected product: pcis Laiser Tag. 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-9722/ (Markdown: https://insights.sbomify.com/CVE-2026-9722/index.md)","id":"CVE-2026-9722","markdown":"https://insights.sbomify.com/CVE-2026-9722/index.md","name":"CVE-2026-9722","record":{"aliases":["GHSA-rh8x-77pm-8pvm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into updating plugin settings, including API keys, via forged requests due to missing nonce validation.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Laiser Tag plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.5. This is due to missing or incorrect nonce validation on the addOptionsPageFields function. This makes it possible for unauthenticated attackers to update the plugin's settings, including the API key, tag blacklist, relevance threshold, batch size, and tagging toggles, via a forged request via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"Laiser Tag \u003c= 1.2.5 - Cross-Site Request Forgery to Plugin Settings Update via Settings Form","id":"CVE-2026-9722","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Google Plus One Bottom \u003c= 0.0.2 - Cross-Site Request Forgery to Plugin Settings Update via Settings Page","id":"CVE-2026-9723"},"packages":[],"prev":{"headline":"Book a Room Event Calendar \u003c= 1.9 - Cross-Site Request Forgery to Settings Update","id":"CVE-2026-9721"},"products":["Laiser Tag"],"published":"2026-06-02","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-06-02","vendors":["pcis"]},"summary":"Attackers can trick administrators into updating plugin settings, including API keys, via forged requests due to missing nonce validation.","url":"https://insights.sbomify.com/CVE-2026-9722/"}