{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-4869 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-4869 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4869 is a high-severity cross-site scripting vulnerability in wplegalpages Cookie Banner for GDPR / CCPA – WPLP Cookie Consent, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-4869 and fix it if it is affected.\n\nWhat it is: CVE-2024-4869 is a high-severity cross-site scripting vulnerability in wplegalpages Cookie Banner for GDPR / CCPA – WPLP Cookie Consent, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-4869 in the wild and no public exploit code.\n\nAffected product: wplegalpages Cookie Banner for GDPR / CCPA – WPLP Cookie Consent. 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-2024-4869/ (Markdown: https://insights.sbomify.com/CVE-2024-4869/index.md)","id":"CVE-2024-4869","markdown":"https://insights.sbomify.com/CVE-2024-4869/index.md","name":"CVE-2024-4869","record":{"aliases":["GHSA-f82h-5m28-cr2p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via the Client-IP header, leading to stored XSS execution on victim pages.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_cookie_consent","vendor":"wpeka"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 WP Cookie Consent ( for GDPR, CCPA \u0026 ePrivacy ) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘Client-IP’ header in all versions up to, and including, 3.2.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers 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":"Cross-site scripting in Cookie Banner for GDPR / CCPA – WPLP Cookie Consent","id":"CVE-2024-4869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Frontend Registration – Contact Form 7 \u003c= 5.1 - Authenticated (Editor+) Privilege Escalation","id":"CVE-2024-4870"},"packages":[],"prev":{"headline":"Cross-site scripting in Extensions for Elementor","id":"CVE-2024-4868"},"products":["Cookie Banner for GDPR / CCPA – WPLP Cookie Consent"],"published":"2024-06-25","related":[{"cvss_score":5.3,"headline":"Missing authorization in Cookie Banner for GDPR / CCPA – WPLP Cookie Consent","id":"CVE-2024-3599","kev_date_added":null,"published":"2024-05-02"},{"cvss_score":4.3,"headline":"Missing authorization in Cookie Banner for GDPR / CCPA – WPLP Cookie Consent","id":"CVE-2024-11724","kev_date_added":null,"published":"2024-12-12"},{"cvss_score":4,"headline":"WordPress WP Cookie Notice for GDPR, CCPA \u0026 ePrivacy Consent Plugin \u003c= 2.2.5 is vulnerable to CSV Injection","id":"CVE-2023-23678","kev_date_added":null,"published":"2023-11-07"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wplegalpages"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via the Client-IP header, leading to stored XSS execution on victim pages.","url":"https://insights.sbomify.com/CVE-2024-4869/"}