{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9756 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9756 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9756 is a medium-severity cross-site scripting vulnerability in edge22 GenerateBlocks, published on 3 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9756 and fix it if it is affected.\n\nWhat it is: CVE-2026-9756 is a medium-severity cross-site scripting vulnerability in edge22 GenerateBlocks, published on 3 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9756 in the wild and no public exploit code.\n\nAffected product: edge22 GenerateBlocks. 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-9756/ (Markdown: https://insights.sbomify.com/CVE-2026-9756/index.md)","id":"CVE-2026-9756","markdown":"https://insights.sbomify.com/CVE-2026-9756/index.md","name":"CVE-2026-9756","record":{"aliases":["GHSA-735g-4w2p-c7c6"],"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":"low_privilege","summary":"Authenticated contributors can inject JavaScript via the Headline Block link attribute, leading to script execution and potential account takeover when administrators click the link.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 GenerateBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Headline Block 'linkMetaFieldType' Dynamic Link Attribute in all versions up to, and including, 2.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A contributor-level attacker can store a JavaScript payload in their own profile description (allowlisted by get_safe_user_meta_keys()) and prepend 'javascript:' via the linkMetaFieldType attribute, creating a fully attacker-controlled href that executes when any user, including an administrator, clicks the rendered headline 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":"Cross-site scripting in GenerateBlocks","id":"CVE-2026-9756","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"GEO my WP \u003c= 4.5.5 - Unauthenticated SQL Injection via 'swlatlng' / 'nelatlng' Parameters","id":"CVE-2026-9757"},"packages":[],"prev":{"headline":"Stack memory disclosure in filemd5 command","id":"CVE-2026-9754"},"products":["GenerateBlocks"],"published":"2026-07-03","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-06","vendors":["edge22"]},"summary":"Authenticated contributors can inject JavaScript via the Headline Block link attribute, leading to script execution and potential account takeover when administrators click the link.","url":"https://insights.sbomify.com/CVE-2026-9756/"}