CVE-2018-19207
Van-Ons Wp-Gdpr-Compliance ≤ 1.4.3
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2018-19207 is a critical-severity Forced Browsing (CWE-425) vulnerability in Van-Ons Wp-Gdpr-Compliance. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2018-10916
Vulnerability Data
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.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Forcing a decision on every access request, including direct ones, reduces the exploitability of forced browsing by ensuring no unchecked access paths.
Forces all accesses through the reference monitor, preventing direct or forced requests that bypass checks.
Enforcing access for all logical requests prevents unauthorized direct access to protected resources.
Displaying the notification before further access on public systems prevents direct resource requests from bypassing the required system use terms and consent.
Decoy endpoints catch forced browsing and direct requests, deflecting attackers from legitimate resources while enabling analysis.
Blocks unauthorized direct requests or forced browsing by denying input access to non-authorized actors.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.
Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.
Access control policy directly requires authorization checks on all resources, preventing forced browsing.
Managing access rights ensures every URL/script/file is explicitly authorized, mitigating direct request attacks.
Privileged access rights control enforces least-privilege checks on restricted endpoints.
Secure SDLC can include authorization design, yet the control itself does not guarantee runtime enforcement.