{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9269 exists.","fix":"No fix has been published for CVE-2026-9269 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9269 is a low-severity cross-site scripting vulnerability in Unknown Secure Copy Content Protection and Content Locking, published on 12 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-9269 and fix it if it is affected.\n\nWhat it is: CVE-2026-9269 is a low-severity cross-site scripting vulnerability in Unknown Secure Copy Content Protection and Content Locking, published on 12 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-9269 exists.\n\nAffected product: Unknown Secure Copy Content Protection and Content Locking. 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-9269/ (Markdown: https://insights.sbomify.com/CVE-2026-9269/index.md)","id":"CVE-2026-9269","markdown":"https://insights.sbomify.com/CVE-2026-9269/index.md","name":"CVE-2026-9269","record":{"aliases":["GHSA-fxh5-p8jw-9g3v"],"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":"Admins can inject malicious scripts via unsanitized settings, enabling stored XSS attacks in WordPress multisite environments.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"The Secure Copy Content Protection and Content Locking WordPress plugin before 5.1.5 does not sanitise and escape some of its settings, 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":"Secure Copy Content Protection and Content Locking \u003c 5.1.5 - Admin+ Stored XSS via ays_sccp_sub_icon_image Parameter","id":"CVE-2026-9269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"DataDog::DogStatsd versions through 0.07 for Perl allow metric injections","id":"CVE-2026-9270"},"packages":[],"prev":{"headline":"Incorrect Authorization in GitLab","id":"CVE-2026-9268"},"products":["Secure Copy Content Protection and Content Locking"],"published":"2026-06-12","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-12","vendors":["Unknown"]},"summary":"Admins can inject malicious scripts via unsanitized settings, enabling stored XSS attacks in WordPress multisite environments.","url":"https://insights.sbomify.com/CVE-2026-9269/"}