{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0220 exists.","fix":"No fix has been published for CVE-2022-0220 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0220 is a medium-severity cross-site scripting vulnerability in Unknown WordPress GDPR, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-0220 and fix it if it is affected.\n\nWhat it is: CVE-2022-0220 is a medium-severity cross-site scripting vulnerability in Unknown WordPress GDPR, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, 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-2022-0220 exists.\n\nAffected product: Unknown WordPress GDPR. 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-2022-0220/ (Markdown: https://insights.sbomify.com/CVE-2022-0220/index.md)","id":"CVE-2022-0220","markdown":"https://insights.sbomify.com/CVE-2022-0220/index.md","name":"CVE-2022-0220","record":{"aliases":["GHSA-7c99-6mgq-969f"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress GDPR plugin","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary JavaScript in victims' browsers via reflected XSS in the WordPress GDPR plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wordpress_gdpr\\\u0026ccpa","vendor":"welaunch"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"The check_privacy_settings AJAX action of the WordPress GDPR WordPress plugin before 1.9.27, available to both unauthenticated and authenticated users, responds with JSON data without an \"application/json\" content-type. Since an HTML payload isn't properly escaped, it may be interpreted by a web browser led to this endpoint. Javascript code may be executed on a victim's browser. Due to v1.9.26 adding a CSRF check, the XSS is only exploitable against unauthenticated users (as they all share the same nonce)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-0220.yaml","stars":null,"title":"WordPress GDPR \u0026 CCPA \u003c1.9.27 - Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"WordPress GDPR \u0026 CCPA \u003c 1.9.27 - Unauthenticated Reflected Cross-Site Scripting","id":"CVE-2022-0220","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"XML external entity in SCADAPack Workbench","id":"CVE-2022-0221"},"packages":[],"prev":{"headline":"Improper Restriction of XML External Entity Reference in skylot/jadx","id":"CVE-2022-0219"},"products":["WordPress GDPR"],"published":"2022-02-01","related":[{"cvss_score":9.6,"headline":"WordPress GDPR \u0026 CCPA \u003c 1.9.26 - Authenticated Reflected Cross-Site Scripting","id":"CVE-2021-24814","kev_date_added":null,"published":"2022-02-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Unauthenticated attackers can execute arbitrary JavaScript in victims' browsers via reflected XSS in the WordPress GDPR plugin.","url":"https://insights.sbomify.com/CVE-2022-0220/"}