{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5293 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5293 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5293 is a medium-severity cross-site scripting vulnerability in olivesystem 診断ジェネレータ作成プラグイン, published on 20 May 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-5293 and fix it if it is affected.\n\nWhat it is: CVE-2026-5293 is a medium-severity cross-site scripting vulnerability in olivesystem 診断ジェネレータ作成プラグイン, published on 20 May 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-5293 in the wild and no public exploit code.\n\nAffected product: olivesystem 診断ジェネレータ作成プラグイン. 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-5293/ (Markdown: https://insights.sbomify.com/CVE-2026-5293/index.md)","id":"CVE-2026-5293","markdown":"https://insights.sbomify.com/CVE-2026-5293/index.md","name":"CVE-2026-5293","record":{"aliases":["GHSA-9hmw-83v5-qm22"],"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 subscribers can inject malicious scripts into theme files via the js parameter, leading to stored XSS execution for other users.","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 診断ジェネレータ作成プラグイン (Diagnosis Generator) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'js' parameter in versions up to and including 1.4.16. This is due to missing authorization checks and insufficient input sanitization in the themeFunc() function. The function is hooked to 'admin_init' and processes theme update requests without verifying user capabilities, allowing any authenticated user (including subscribers) to save malicious JavaScript to theme files. Additionally, the save() function uses stripslashes() which removes WordPress's magic quotes protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in theme files that will execute whenever a user accesses a page containing the diagnosis form shortcode.","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":"診断ジェネレータ作成プラグイン \u003c= 1.4.16 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'js' Parameter","id":"CVE-2026-5293","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Missing authorization in GeekyBot — AI Copilot, Chatbot, WooCommerce Lead Gen \u0026 Zero-Prompt Content","id":"CVE-2026-5294"},"packages":[],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2026-5292"},"products":["診断ジェネレータ作成プラグイン"],"published":"2026-05-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-05-20","vendors":["olivesystem"]},"summary":"Authenticated subscribers can inject malicious scripts into theme files via the js parameter, leading to stored XSS execution for other users.","url":"https://insights.sbomify.com/CVE-2026-5293/"}