{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3368 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3368 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3368 is a high-severity cross-site scripting vulnerability in fahadmahmood Injection Guard, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3368 and fix it if it is affected.\n\nWhat it is: CVE-2026-3368 is a high-severity cross-site scripting vulnerability in fahadmahmood Injection Guard, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3368 in the wild and no public exploit code.\n\nAffected product: fahadmahmood Injection Guard. 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-3368/ (Markdown: https://insights.sbomify.com/CVE-2026-3368/index.md)","id":"CVE-2026-3368","markdown":"https://insights.sbomify.com/CVE-2026-3368/index.md","name":"CVE-2026-3368","record":{"aliases":["GHSA-9hg7-qjwm-hfxv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject scripts via query parameters that execute in the admin log page, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 Injection Guard plugin for WordPress is vulnerable to Stored Cross-Site Scripting via malicious query parameter names in all versions up to and including 1.2.9. This is due to insufficient input sanitization in the sanitize_ig_data() function which only sanitizes array values but not array keys, combined with missing output escaping in the ig_settings.php template where stored parameter keys are echoed directly into HTML. When a request is made to the site, the plugin captures the query string via $_SERVER['QUERY_STRING'], applies esc_url_raw() (which preserves URL-encoded special characters like %22, %3E, %3C), then passes it to parse_str() which URL-decodes the string, resulting in decoded HTML/JavaScript in the array keys. These keys are stored via update_option('ig_requests_log') and later rendered without esc_html() or esc_attr() on the admin log page. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in the admin log page that execute whenever an administrator views the Injection Guard log interface.","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":"Injection Guard \u003c= 1.2.9 - Unauthenticated Stored Cross-Site Scripting via Query Parameter Name","id":"CVE-2026-3368","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":18,"next":{"headline":"Cross-site scripting in Better Find and Replace – AI-Powered Suggestions","id":"CVE-2026-3369"},"packages":[],"prev":{"headline":"Cross-site scripting in Lockme calendars integration","id":"CVE-2026-3367"},"products":["Injection Guard"],"published":"2026-03-20","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["fahadmahmood"]},"summary":"Unauthenticated attackers can inject scripts via query parameters that execute in the admin log page, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-3368/"}