{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5217 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5217 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5217 is a high-severity cross-site scripting vulnerability in Optimole – Optimize Images in Real Time, published on 11 Apr 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-5217 and fix it if it is affected.\n\nWhat it is: CVE-2026-5217 is a high-severity cross-site scripting vulnerability in Optimole – Optimize Images in Real Time, published on 11 Apr 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-5217 in the wild and no public exploit code.\n\nAffected product: Optimole – Optimize Images in Real Time. 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-5217/ (Markdown: https://insights.sbomify.com/CVE-2026-5217/index.md)","id":"CVE-2026-5217","markdown":"https://insights.sbomify.com/CVE-2026-5217/index.md","name":"CVE-2026-5217","record":{"aliases":["GHSA-8g9h-q4wq-r7gp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via the srcset descriptor parameter in the Optimole 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":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 Optimole – Optimize Images | Convert WebP \u0026 AVIF | CDN \u0026 Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 4.2.2. This is due to insufficient input sanitization and output escaping on the user-supplied 's' parameter (srcset descriptor) in the unauthenticated /wp-json/optimole/v1/optimizations REST endpoint. The endpoint validates requests using an HMAC signature and timestamp, but these values are exposed directly in the frontend HTML making them accessible to any visitor. The plugin uses sanitize_text_field() on the descriptor value of rest.php, which strips HTML tags but does not escape double quotes. The poisoned descriptor is then stored via transients (backed by the WordPress options table) and later retrieved and injected verbatim into the srcset attribute of tag_replacer.php without proper escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts into pages that will execute whenever a user accesses the injected page.","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":"Optimole \u003c= 4.2.2 - Unauthenticated Stored Cross-Site Scripting via Srcset Descriptor Parameter","id":"CVE-2026-5217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"HTML Injection in Softtr's E-Commerce Pack","id":"CVE-2026-5218"},"packages":[],"prev":{"headline":"D-Link DNS-1550-04 network_mgr.cgi cgi_get_ipv6 access control","id":"CVE-2026-5215"},"products":["Optimole – Optimize Images in Real Time"],"published":"2026-04-11","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-13","vendors":["optimole"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via the srcset descriptor parameter in the Optimole WordPress plugin, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-5217/"}