{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-19207 exists.","fix":"No fix has been published for CVE-2018-19207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19207 is a critical code injection vulnerability in n/a, published on 12 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19207 and fix it if it is affected.\n\nWhat it is: CVE-2018-19207 is a critical code injection vulnerability in n/a, published on 12 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-19207 exists.\n\nAffected product: n/a. 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-2018-19207/ (Markdown: https://insights.sbomify.com/CVE-2018-19207/index.md)","id":"CVE-2018-19207","markdown":"https://insights.sbomify.com/CVE-2018-19207/index.md","name":"CVE-2018-19207","record":{"aliases":["GHSA-q4mw-9w8q-q3fp"],"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":"Remote attackers can execute arbitrary code in the WP GDPR Compliance plugin due to mishandled database input, requiring immediate upgrades.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wp-gdpr-compliance","vendor":"van-ons"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-425","name":"Direct Request"}],"description":"The Van Ons WP GDPR Compliance (aka wp-gdpr-compliance) plugin before 1.4.3 for WordPress allows remote attackers to execute arbitrary code because $wpdb-\u003eprepare() input is mishandled, as exploited in the wild in November 2018.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2018-11-08","github_poc":3,"max_poc_stars":4,"metasploit":1,"nuclei":1,"refs":[{"date":"2018-11-27T14:27:06Z","kind":"github_poc","ref":"https://github.com/aeroot/WP-GDPR-Compliance-Plugin-Exploit","stars":4,"title":"Exploit of the privilege escalation vulnerability of the WordPress plugin \"WP GDPR Compliance\" by \"Van Ons\" (https://de.wordpress.org/plugins/wp-gdpr-compliance/) CVE-2018-19207"},{"date":"2025-09-01T11:39:42Z","kind":"github_poc","ref":"https://github.com/AnotherSec/CVE-2018-19207","stars":1,"title":"WP GDPR Compliance \u003c= 1.4.2  - Remote Code Execution (exploiter)"},{"date":"2018-11-08","kind":"metasploit","ref":"auxiliary/admin/http/wp_gdpr_compliance_privesc","stars":null,"title":"WordPress WP GDPR Compliance Plugin Privilege Escalation"},{"date":"2019-03-15T18:09:58Z","kind":"github_poc","ref":"https://github.com/cved-sources/cve-2018-19207","stars":0,"title":"cve-2018-19207"},{"date":null,"kind":"nuclei","ref":"http/cves/2018/CVE-2018-19207.yaml","stars":null,"title":"WP GDPR Compliance \u003c 1.4.3 - Unauthenticated Call Any Action or Update Any Option"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2018-19207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Null dereference in n/a","id":"CVE-2018-19208"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19206"},"products":["n/a"],"published":"2018-11-12","related":[],"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":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code in the WP GDPR Compliance plugin due to mishandled database input, requiring immediate upgrades.","url":"https://insights.sbomify.com/CVE-2018-19207/"}