# CVE-2018-19207: Code injection in n/a

> Remote attackers can execute arbitrary code in the WP GDPR Compliance plugin due to mishandled database input, requiring immediate upgrades.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q4mw-9w8q-q3fp

## What is CVE-2018-19207?

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.

### Official 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->prepare() input is mishandled, as exploited in the wild in November 2018.

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2018-19207?

It affects 1 product.


Products: Van-Ons Wp-Gdpr-Compliance.

## How do I fix CVE-2018-19207?

No fix has been published for CVE-2018-19207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-19207 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-19207 exists.

Public exploit code:

- 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 (github_poc): https://github.com/aeroot/WP-GDPR-Compliance-Plugin-Exploit
- WP GDPR Compliance <= 1.4.2  - Remote Code Execution (exploiter) (github_poc): https://github.com/AnotherSec/CVE-2018-19207
- WordPress WP GDPR Compliance Plugin Privilege Escalation (metasploit)
- cve-2018-19207 (github_poc): https://github.com/cved-sources/cve-2018-19207
- WP GDPR Compliance < 1.4.3 - Unauthenticated Call Any Action or Update Any Option (nuclei): http/cves/2018/CVE-2018-19207.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19207 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-19207 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-19207/ (Markdown: https://insights.sbomify.com/CVE-2018-19207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-19207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-19207
- OSV: https://osv.dev/vulnerability/CVE-2018-19207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-19207/
Summaries are generated and may contain mistakes; the official description above is the record.