Skip to content

Product

wordpress gdpr-cookie-consent vulnerabilities

28 published CVES affecting wordpress gdpr-cookie-consent, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
28
Critical
2
High
6
Medium
20
Low
0
Unscored
0
CISA KEV
0

Latest wordpress gdpr-cookie-consent CVEs

Newest publication first · page 1 of 2

  1. MediumCVSS 6.5 EPSS 0.20%

    The WPLP Cookie Consent WordPress plugin before 4.4.4 does not perform CSRF or capability checks when processing bulk actions on its administration screens, and does not restrict the targeted items to its own records, allowing attackers to make a logged in admin permanently delet...

  2. MediumCVSS 4.3 EPSS 0.34%

    The GDPR Cookie Consent plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check and missing nonce verification on the gdpr_cookie_consent_ajax_save_schedule_scan() function (the wp_ajax_gcc_save_schedule_scan AJAX action) in versi...

  3. HighCVSS 7.5 EPSS 0.43%

    The GDPR Cookie Consent plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'gdpr/v1/settings' REST API endpoint in all versions up to, and including, 4.1.2. This makes it possible for unauthenticated attackers to retrieve se...

  4. MediumCVSS 5.3 EPSS 0.29%

    The Cookie Banner, Cookie Consent, Consent Log, Cookie Scanner, Script Blocker (for GDPR, CCPA & ePrivacy) : WP Cookie Consent plugin for WordPress is vulnerable to unauthorized data modification due to a missing capability check on the gdpr_delete_policy_data function in all ver...

  5. MediumCVSS 4.3 EPSS 0.33%

    The Cookie Consent for WP – Cookie Consent, Consent Log, Cookie Scanner, Script Blocker (for GDPR, CCPA & ePrivacy) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpl_script_save AJAX action in all versions up to,...

  6. MediumCVSS 6.3 EPSS 0.44%

    The Freemius SDK, as used by hundreds of WordPress plugin and theme developers, was vulnerable to Cross-Site Request Forgery and Information disclosure due to missing capability checks and nonce protection on the _get_debug_log, _get_db_option, and the _set_db_option functions in...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.