{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-11997 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-11997 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11997 is a medium-severity vulnerability in seo_tools Bulk SEO Image, published on 24 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-11997 and fix it if it is affected.\n\nWhat it is: CVE-2026-11997 is a medium-severity vulnerability in seo_tools Bulk SEO Image, published on 24 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-11997 in the wild and no public exploit code.\n\nAffected product: seo_tools Bulk SEO Image. 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-11997/ (Markdown: https://insights.sbomify.com/CVE-2026-11997/index.md)","id":"CVE-2026-11997","markdown":"https://insights.sbomify.com/CVE-2026-11997/index.md","name":"CVE-2026-11997","record":{"aliases":["GHSA-pphr-r45w-j4jp"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into bulk-overwriting image ALT-text metadata across the site via a forged request.","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 Bulk SEO Image plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to and including 1.1. This is due to missing or incorrect nonce validation on the plugin's settings page handler BulkSeoImage(), which dispatches to launchbulk() / BulkSeoImageGo() whenever the request contains $_POST['bulkseoimage']. No wp_nonce_field() is emitted in the form and no check_admin_referer()/wp_verify_nonce() is performed before bulk-overwriting the _wp_attachment_image_alt post meta for every image attached to every published post and/or page. This makes it possible for unauthenticated attackers to bulk-overwrite image ALT-text metadata across the site 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":"Bulk SEO Image \u003c= 1.1 - Cross-Site Request Forgery to Settings Update","id":"CVE-2026-11997","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"AngularJS XSS via SCE resource URL sanitization bypass","id":"CVE-2026-11998"},"packages":[],"prev":{"headline":"Advanced Popups \u003c= 1.2.3 - Authenticated (Author+) Stored Cross-Site Scripting via 'Notification Button Link' Field","id":"CVE-2026-11996"},"products":["Bulk SEO Image"],"published":"2026-06-24","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-24","vendors":["seo_tools"]},"summary":"Unauthenticated attackers can trick administrators into bulk-overwriting image ALT-text metadata across the site via a forged request.","url":"https://insights.sbomify.com/CVE-2026-11997/"}