dbcve.org
Gdpr Compliance \& Cookie ConsentWordPress extension · Stylemixthemes

CVE-2022-45815

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in StylemixThemes GDPR Compliance & Cookie Consent plugin <= 1.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Cross-Site Request Forgery (CSRF) vulnerability in the StylemixThemes GDPR Compliance & Cookie Consent plugin allows attackers to trick authenticated administrators into performing unintended actions, such as modifying cookie consent settings or disabling GDPR compliance features, potentially exposing user data to unauthorized collection.

MitigationUpdate the plugin to the latest version if available; otherwise, implement WordPress nonce verification on all state-changing actions (forms and AJAX endpoints) within the plugin to prevent CSRF attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gdpr Compliance \& Cookie ConsentWordPress extension
Affected:<= 1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'GDPR Compliance & Cookie Consent' by Stylemixthemes, or check the plugin files in wp-content/plugins/ for a folder containing 'gdpr' or 'cookie-consent'
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    Check the plugin header in its main PHP file (usually named index.php or the plugin's main PHP file) for the 'Version' comment, or view the plugin details in WordPress admin Plugins page
    Affected if Version is 1.2 or lower (any version <= 1.2)
  3. Verify admin user role exists
    In WordPress admin, go to Users > All Users and check if any users with Administrator role exist; CSRF attacks target authenticated administrators
    Affected if There is at least one user with Administrator role who can access the plugin settings
  4. Inspect plugin for missing nonce verification
    Examine the plugin's PHP files for form submissions and AJAX handlers (look for functions like wp_ajax_, admin_post_, and form action attributes); check if these handlers verify nonces using wp_verify_nonce or check_admin_referer
    Affected if State-changing actions (forms modifying settings, AJAX endpoints changing options) lack nonce verification before processing

A user is affected if the GDPR Compliance & Cookie Consent plugin version is 1.2 or lower, an administrator can be authenticated, and the plugin processes requests without verifying anti-CSRF tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2
Interim mitigation

Update the plugin to the latest version if available; otherwise, implement WordPress nonce verification on all state-changing actions (forms and AJAX endpoints) within the plugin to prevent CSRF attacks.

Recommended fix Moderate confidence

Upgrade to the latest version of Gdpr Compliance & Cookie Consent plugin (version > 1.2)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Gdpr Compliance & Cookie Consent' plugin by StylemixThemes
  4. Deactivate and delete the current version of the plugin
  5. Install the latest available version of the plugin from the WordPress plugin repository
  6. Activate the newly installed version
  7. Verify the plugin is functioning correctly and settings are intact
Caveat Review plugin settings after upgrade as minor configuration changes may occur with major version updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gdpr Compliance \& Cookie Consent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45815 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data