dbcve.org
Gdpr Cookie Consent BannerWordPress extension · Termly

CVE-2024-35692

HIGH · 7.3 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 3.2.1 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in Termly Cookie Consent.This issue affects Cookie Consent: from n/a through 3.2.

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 · moderate confidence

A missing authorization vulnerability exists in the Termly Cookie Consent plugin versions through 3.2, allowing unauthenticated or unauthorized users to access certain functionality that should be restricted. The specific attack vector and affected endpoints are not detailed in the available information, but authorization bypass vulnerabilities typically enable users to perform actions outside their privilege level.

MitigationUpdate to the latest version of the Termly Cookie Consent plugin when available. If no update exists, review the plugin's access control logic and implement proper capability checks and nonce verification for all administrative functions.

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 Cookie Consent BannerWordPress extension
Affected:< 3.2.1

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify Termly Cookie Consent installation
    Check your WordPress site's plugin directory for 'Termly GDPR Cookie Consent' or 'termly-cookie-consent' plugin folder, or list installed plugins via WP-CLI: wp plugin list --search='termly'
    Affected if The plugin is not present in the installed plugins list
  2. Determine installed plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate the Termly GDPR Cookie Consent banner plugin, and note the version number displayed, or use WP-CLI: wp plugin get termly-gdpr-cookie-consent --field=version
    Affected if Version displayed is 3.2 or below, or the version field cannot be read or is missing
  3. Compare version against affected range
    Review the noted version number against the affected range: any version less than 3.2.1 is vulnerable
    Affected if Installed version is 3.2, 3.1, 3.0, 2.x, or any version number lower than 3.2.1
  4. Verify unauthorized access exposure (if version is vulnerable)
    Test whether unauthenticated or low-privilege users can access plugin admin functions by examining if the wp-admin/admin-ajax.php or admin-post.php endpoints related to termly actions respond without requiring authentication, or review server access logs for unexpected termly-related requests from unauthenticated IPs
    Affected if Unauthenticated requests to termly-related AJAX or admin actions return successful responses instead of requiring login or returning 401/403 errors

You are affected if the Termly GDPR Cookie Consent plugin is installed and the installed version is 3.2 or lower (less than 3.2.1), since this version range contains the missing authorization vulnerability that allows unauthorized access to restricted functionality.

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 3.2.1 or later
Fixed in 3.2.1
Interim mitigation

Update to the latest version of the Termly Cookie Consent plugin when available. If no update exists, review the plugin's access control logic and implement proper capability checks and nonce verification for all administrative functions.

Recommended fix High confidence

3.2.1

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find 'Gdpr Cookie Consent Banner' (or 'Termly Cookie Consent') in the plugin list
  4. Click 'Update now' or visit the plugin details page and install version 3.2.1
  5. Verify the plugin version shows 3.2.1 after updating
  6. Test that the cookie consent functionality works correctly

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

Fix this in Gdpr Cookie Consent Banner Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35692 — 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-2024-35692 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