{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82127 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82127 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82127 is a low-severity cross-site scripting vulnerability in Unknown Schema \u0026 Structured Data for WP \u0026 AMP, published on 30 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-82127 and fix it if it is affected.\n\nWhat it is: CVE-2026-82127 is a low-severity cross-site scripting vulnerability in Unknown Schema \u0026 Structured Data for WP \u0026 AMP, published on 30 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-82127 in the wild and no public exploit code.\n\nAffected product: Unknown Schema \u0026 Structured Data for WP \u0026 AMP. 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-82127/ (Markdown: https://insights.sbomify.com/CVE-2026-82127/index.md)","id":"CVE-2026-82127","markdown":"https://insights.sbomify.com/CVE-2026-82127/index.md","name":"CVE-2026-82127","record":{"aliases":["GHSA-7x27-h8wx-cfpr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Editors can inject scripts via taxonomy fields in multisite installs, leading to XSS when viewed by admins.","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":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Schema \u0026 Structured Data for WP \u0026 AMP WordPress plugin before 1.67 does not perform a capability check when saving several of its fields, nor escape them when outputting them back, allowing users with the editor role and above to inject arbitrary web scripts that execute when a higher privileged user views the affected screen. This is only exploitable on multisite installs, where editors do not hold the unfiltered_html capability.","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":"Schema \u0026 Structured Data for WP \u0026 AMP \u003c 1.67 - Editor+ Stored XSS via Taxonomy Term Fields","id":"CVE-2026-82127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in OS Recovery Tool","id":"CVE-2026-82153"},"packages":[],"prev":{"headline":"Missing authorization in Schema \u0026 Structured Data for WP \u0026 AMP","id":"CVE-2026-82126"},"products":["Schema \u0026 Structured Data for WP \u0026 AMP"],"published":"2026-09-30","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-09-30","vendors":["Unknown"]},"summary":"Editors can inject scripts via taxonomy fields in multisite installs, leading to XSS when viewed by admins.","url":"https://insights.sbomify.com/CVE-2026-82127/"}