Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2018-19207

WP GDPR Compliance

Van Ons / WP GDPR Compliance

Severity
CVSS 9.8 · Critical
Confidence
High
Exploit status
Exploited in the wild
EPSS
88.1%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2018-19207 is an unauthenticated vulnerability affecting Van Ons WP GDPR Compliance. The Van Ons WP GDPR Compliance (aka wp-gdpr-compliance) plugin before 1.4.3 for WordPress allows remote attackers to execute...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Van Ons / WP GDPR Compliance.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

WP GDPR Compliance

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.

Published
12 Nov 2018
Exploitation Reported
12 Nov 2018
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

wordpress nuclei_scanner

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CVE

Recorded 12 Nov 2018

A trusted third party reported exploitation.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2018-11-12 17:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.0

9.8 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

88.1%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

All CVSS Scores

CVSS v3.0 9.8 Critical

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS v2.0 7.5 High

AV:N/AC:L/Au:N/C:P/I:P/A:P

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. 14:20 UTC

    Public PoC available

    Public proof-of-concept code published

  2. 15:34 UTC

    Nuclei template available

    Scanner coverage available

  3. 17:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  4. 17:00 UTC

    CVE published

    Vulnerability disclosed publicly

  5. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2018-19207

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2018-19207",
  "confidence": "High",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.88065,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}