LiveActive security incident?Get immediate response
CVE Record

CVE-2024-33682: WordPress WP GDPR Compliance plugin <= 2.0.23 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Cookie Information A/S WP GDPR Compliance.This issue affects WP GDPR Compliance: from n/a through 2.0.23.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the WordPress WP GDPR Compliance plugin through version 2.0.23. A successful attack would require user interaction and could cause limited unauthorized changes or disruption. The provided sources do not show active exploitation or a named fixed version.

Executive priority

Treat this as a routine but real web-platform risk. Prioritize sites that handle privacy consent, customer-facing WordPress properties, and environments with many administrators. It is not currently evidenced as actively exploited in the provided sources.

Technical view

CVE-2024-33682 is CWE-352 affecting Cookie Information A/S WP GDPR Compliance through 2.0.23. CVSS 3.1 is 5.4: network attack vector, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites with the WP GDPR Compliance plugin installed at version 2.0.23 or earlier. Sites not using this plugin, or using unaffected versions, are not indicated as affected in the provided sources.

Exploitation context

The source bundle lists no CISA KEV entry and does not cite active exploitation. The CVSS vector requires user interaction, consistent with CSRF. Public vulnerability records exist, but the provided evidence does not include exploit details or observed attacks.

Researcher notes

The available evidence is sparse: CVE metadata, Patchstack reference, affected range, CWE, and CVSS. Avoid assuming the vulnerable action, required victim role, exploit availability, or fixed version without vendor or Patchstack details beyond the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for WP GDPR Compliance plugin usage and version.
  • Check vendor and Patchstack guidance for a fixed version or official mitigation.
  • Update the plugin if an official safe version is available.
  • Disable or remove the plugin where it is unnecessary or cannot be safely updated.
  • Restrict administrative access and reinforce phishing-resistant workflows for privileged users.

Validation and detection

  • Confirm whether WP GDPR Compliance is installed and enabled on each WordPress site.
  • Record installed plugin versions and flag versions through 2.0.23.
  • Review plugin settings for unexpected changes after the disclosure date.
  • Verify sensitive plugin actions use CSRF protections such as nonces or equivalent controls.
  • Monitor vendor advisories for patch status and remediation updates.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-33682 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2024-33682Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Cookie Information A/SWP GDPR Compliancewp-gdpr-compliance, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.