CVE-2018-19207
Exploitation reported by one source. First attested on 2018-11-12 by GCVE · kevintel.
- Published2018-11-12
- Fixed in1.4.3
- WeaknessCWE-425
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2018-11-1217:00Listed as exploited by GCVEGCVE
- 2018-11-1217:00Exploitation first reportedGCVE
- 2018-11-1217:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-11-04 03:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-19207?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-19207?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.4 | < 1.4.3 | 1.4.3 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Van-ons wp-gdpr-compliance to 1.4.3
Advisories and patches
- wordpress.orgVendor Advisory
Detection
read 2026-11-03 22:42 UTC- Nuclei template
- available ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 3 repositories, unverifiedaeroot/WP-GDPR-Compliance-Plugin-Exploitcved-sources/cve-2018-19207AnotherSec/CVE-2018-19207 PoC-in-GitHub
- Metasploit modules
- 1 moduleauxiliary/admin/http/wp_gdpr_compliance_privescrank: normalModule metadata: Metasploit Framework, © Rapid7, Inc., BSD-3-Clause. Metasploit Framework
Sources
- GCVEexploitation2018-11-12
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-425read 2026-10-23
- FIRST EPSSEPSS score88.1 %read 2026-11-03
- PoC-in-GitHubproof of concept3read 2026-11-03
- ProjectDiscoverydetectionread 2026-11-03
- Metasploit FrameworkMetasploit modules1known since 2026-11-01
Identifiers
- EUVD-2018-10916same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- auxiliary/admin/http/wp_gdpr_compliance_privescexploit moduleMetasploit Framework © Rapid7 · BSD-3-Clause
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-11-12
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-19207?
Is CVE-2018-19207 actively exploited?
What is the CVSS score for CVE-2018-19207?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GCVE · GCVE dump terms (preserve source attribution)
- Metasploit Framework · BSD-3-Clause
- Nuclei templates · MIT
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0