{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9677 exists.","fix":"No fix has been published for CVE-2026-9677 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9677 is a medium-severity cross-site scripting vulnerability in Unknown Shariff for WordPress, published on 27 Jun 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-9677 and fix it if it is affected.\n\nWhat it is: CVE-2026-9677 is a medium-severity cross-site scripting vulnerability in Unknown Shariff for WordPress, published on 27 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9677 exists.\n\nAffected product: Unknown Shariff for WordPress. 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-9677/ (Markdown: https://insights.sbomify.com/CVE-2026-9677/index.md)","id":"CVE-2026-9677","markdown":"https://insights.sbomify.com/CVE-2026-9677/index.md","name":"CVE-2026-9677","record":{"aliases":["GHSA-vm7c-g967-fj52"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Admin users can inject malicious scripts via the shariff_infourl setting, leading to stored XSS attacks on the frontend.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"The Shariff for WordPress Shariff for WordPress plugin through 1.0.11 does not sanitize or escape the shariff_infourl setting before outputting it in the frontend HTML via the generateshariff() function, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Shariff for WordPress \u003c= 1.0.11 - Admin+ Stored Cross-Site Scripting","id":"CVE-2026-9677","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"undici vulnerable to cross-user information disclosure via shared cache whitespace bypass","id":"CVE-2026-9678"},"packages":[],"prev":{"headline":"f4 Post Tree \u003c 2.0.5 - Subscriber+ Arbitrary Post Parent/Menu Order Modification","id":"CVE-2026-9676"},"products":["Shariff for WordPress"],"published":"2026-06-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-29","vendors":["Unknown"]},"summary":"Admin users can inject malicious scripts via the shariff_infourl setting, leading to stored XSS attacks on the frontend.","url":"https://insights.sbomify.com/CVE-2026-9677/"}