{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9626 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9626 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9626 is a medium-severity cross-site scripting vulnerability in parorrey JSON API User, published on 3 Jul 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-9626 and fix it if it is affected.\n\nWhat it is: CVE-2026-9626 is a medium-severity cross-site scripting vulnerability in parorrey JSON API User, published on 3 Jul 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-9626 in the wild and no public exploit code.\n\nAffected product: parorrey JSON API User. 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-9626/ (Markdown: https://insights.sbomify.com/CVE-2026-9626/index.md)","id":"CVE-2026-9626","markdown":"https://insights.sbomify.com/CVE-2026-9626/index.md","name":"CVE-2026-9626","record":{"aliases":["GHSA-4689-rgvq-62r3"],"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 the comment content 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 JSON API User plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'content' parameter of the post_comment API endpoint in versions up to, and including, 4.1.0 This is due to insufficient input sanitization in the post_comment() function, which passes the attacker-controlled comment_content value directly to wp_insert_comment() without applying any HTML sanitization, and additionally allows the caller to set comment_approved=1 to self-approve the comment and bypass moderation. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an 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":"JSON API User \u003c= 4.1.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'content' Parameter","id":"CVE-2026-9626","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"UTT HiPER 1200GW Web Management setSysAdm strcpy buffer overflow","id":"CVE-2026-9627"},"packages":[],"prev":{"headline":"RSLinx Classic® - Multiple Vulnerabilities","id":"CVE-2026-9625"},"products":["JSON API User"],"published":"2026-07-03","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-07-06","vendors":["parorrey"]},"summary":"Authenticated attackers can inject arbitrary scripts via the comment content parameter, leading to stored XSS execution for other users.","url":"https://insights.sbomify.com/CVE-2026-9626/"}