{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-88997 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-88997 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-88997 is a medium-severity cross-site scripting vulnerability in Unknown JSM Show Post Metadata, published on 23 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-88997 and fix it if it is affected.\n\nWhat it is: CVE-2026-88997 is a medium-severity cross-site scripting vulnerability in Unknown JSM Show Post Metadata, published on 23 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-88997 in the wild and no public exploit code.\n\nAffected product: Unknown JSM Show Post Metadata. 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-88997/ (Markdown: https://insights.sbomify.com/CVE-2026-88997/index.md)","id":"CVE-2026-88997","markdown":"https://insights.sbomify.com/CVE-2026-88997/index.md","name":"CVE-2026-88997","record":{"aliases":["GHSA-w38r-xjmg-mmg7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Contributors can inject JavaScript via post meta keys, leading to session hijacking of higher-privileged users reviewing posts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The JSM Show Post Metadata WordPress plugin before 4.9.1 does not properly escape a post meta key before outputting it into an inline event-handler attribute in an admin-facing meta box, allowing users with contributor-level access and above to inject arbitrary JavaScript that executes in the session of a higher-privileged user who reviews the affected post.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-21","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-21T17:09:02Z","kind":"github_poc","ref":"https://github.com/pervinzahidli/CVE-2026-88997","stars":0,"title":"JSM Show Post Metadata \u003c 4.9.1 - Contributor+ Stored XSS via Custom Field Meta Key"}],"tier":"poc_unverified"},"has_fix":null,"headline":"JSM Show Post Metadata \u003c 4.9.1 - Contributor+ Stored XSS via Custom Field Meta Key","id":"CVE-2026-88997","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Tickera \u003c 3.6.0.4 - Unauthenticated Order Payment Bypass via 2Checkout IPN","id":"CVE-2026-88998"},"packages":[],"prev":{"headline":"WPForms \u003c= 2.0.2 - Reflected Cross-Site Scripting via 'page_title' POST Parameter","id":"CVE-2026-88996"},"products":["JSM Show Post Metadata"],"published":"2026-09-23","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["Unknown"]},"summary":"Contributors can inject JavaScript via post meta keys, leading to session hijacking of higher-privileged users reviewing posts.","url":"https://insights.sbomify.com/CVE-2026-88997/"}