Skip to content
Fencer Intel
critical 9.8

CVE-2018-19207 in the critical feed json

The Van Ons WP GDPR Compliance (aka wp-gdpr-compliance) plugin before 1.4.3 for WordPress allows remote attackers to execute arbitrary code…

published 7y ago modified 4mo ago also EUVD-2018-10916

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
88.1%
EPSS 88.1% chance of exploitation in 30 days, percentile 99.7%
public exploits
1
Metasploit, plus a Nuclei check

Summary

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.

Patch / fix

  • van-ons wp-gdpr-compliance 1.4.3

Is CVE-2018-19207 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit auxiliary/admin/http/wp_gdpr_compliance_privesc)
  2. Published

Exploit prediction

88.07% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit auxiliary/admin/http/wp_gdpr_compliance_privesc WordPress WP GDPR Compliance Plugin Privilege Escalation metasploit auxiliary, normal rank, 2018-11-08
  • Nuclei template WP GDPR Compliance < 1.4.3 - Unauthenticated Call Any Action or Update Any Option nuclei detection template
  • wpvulndb.com https://wpvulndb.com/vulnerabilities/9144 referenced PoC, tagged "exploit" by a source, unverified
  • wordfence.com https://www.wordfence.com/blog/2018/11/trends-following-vulnerability-in-wp-gdpr-compliance-plugin/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.