{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-2430 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2430 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2430 is a medium-severity cross-site scripting vulnerability in optimizingmatters Autoptimize, published on 20 Mar 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-2430 and fix it if it is affected.\n\nWhat it is: CVE-2026-2430 is a medium-severity cross-site scripting vulnerability in optimizingmatters Autoptimize, published on 20 Mar 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-2430 in the wild and no public exploit code.\n\nAffected product: optimizingmatters Autoptimize. 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-2430/ (Markdown: https://insights.sbomify.com/CVE-2026-2430/index.md)","id":"CVE-2026-2430","markdown":"https://insights.sbomify.com/CVE-2026-2430/index.md","name":"CVE-2026-2430","record":{"aliases":["GHSA-8wqg-98qw-6h95"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can inject arbitrary scripts via crafted image tags in the Autoptimize WordPress plugin, leading to stored XSS.","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 Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the lazy-loading image processing in all versions up to, and including, 3.1.14. This is due to the use of an overly permissive regular expression in the `add_lazyload` function that replaces all occurrences of `\\ssrc=` in image tags without limiting to the actual attribute. 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 by crafting an image tag where the `src` URL contains a space followed by `src=`, causing the regex to break the HTML structure and promote text inside attribute values into executable HTML attributes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Autoptimize \u003c= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via Lazy-loaded Image Attributes","id":"CVE-2026-2430","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"CM Custom Reports \u003c= 1.2.7 - Reflected Cross-Site Scripting via 'date_from' and 'date_to' Parameters","id":"CVE-2026-2431"},"packages":[],"prev":{"headline":"Community Events \u003c= 1.5.8 - Authenticated (Administrator+) SQL Injection via 'ce_venue_name' CSV Field","id":"CVE-2026-2429"},"products":["Autoptimize"],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["optimizingmatters"]},"summary":"Authenticated attackers can inject arbitrary scripts via crafted image tags in the Autoptimize WordPress plugin, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-2430/"}