dbcve.org
Wp Cookie ChoiceWordPress extension · Wp Cookie Choice Project

CVE-2021-24595

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-18
Fix available
A fix is available. Upgrade to after 1.1.0 or later.
See remediation →
72/100
Remediation priority · Elevated
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
The Wp Cookie Choice WordPress plugin through 1.1.0 is lacking any CSRF check when saving its options, and do not escape them when outputting them in attributes. As a result, an attacker could make a logged in admin change them to arbitrary values including XSS payloads via a CSRF attack.

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

The Wp Cookie Choice WordPress plugin through version 1.1.0 has two vulnerabilities: it lacks CSRF protection when saving plugin options and fails to escape those options when outputting them in HTML attributes. This allows an attacker to craft a malicious page that tricks a logged-in administrator into submitting a request that changes plugin settings to include XSS payloads.

MitigationAdd nonce-based CSRF tokens to all forms that modify plugin settings and implement proper output escaping (esc_attr()) when rendering option values in HTML attributes.

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
Wp Cookie ChoiceWordPress extension
Affected:<= 1.1.0

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
None
Integrity
High
Availability
None

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

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. Verify Wp Cookie Choice plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Wp Cookie Choice' appears in the installed plugins list
    Affected if The plugin is not installed or has been removed, then the vulnerability does not apply
  2. Check installed plugin version
    Click on the plugin in the WordPress plugins admin page to view its version number, or inspect the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if Version is 1.1.0 or lower, the plugin is vulnerable to the issues described
  3. Verify plugin is active
    Check the plugins list in WordPress admin - the plugin must be active for the XSS to be executable
    Affected if Plugin is active and version is 1.1.0 or lower, the stored XSS could be triggered
  4. Confirm missing CSRF protection in settings code
    Examine the plugin's PHP files (typically in wp-content/plugins/wp-cookie-choice/) - look for the function that handles saving plugin options and verify whether a nonce check (wp_verify_nonce or check_admin_referer) is present before processing the form submission
    Affected if No nonce verification is found before saving settings, the CSRF vulnerability exists
  5. Confirm missing output escaping in settings display
    Examine the plugin's PHP files where saved option values are output into HTML attributes (such as input value attributes) - look for instances where option values are echoed without esc_attr() or similar escaping functions
    Affected if Option values are echoed directly into HTML without esc_attr() or equivalent escaping, the XSS vulnerability exists

If the Wp Cookie Choice plugin version 1.1.0 or lower is installed and active, and the code lacks nonce verification on settings forms and escapes output in HTML attributes, the environment is affected by CVE-2021-24595.

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.1.0
Interim mitigation

Add nonce-based CSRF tokens to all forms that modify plugin settings and implement proper output escaping (esc_attr()) when rendering option values in HTML attributes.

Recommended fix Moderate confidence

latest available version (check WordPress plugin repository for version > 1.1.0)

  1. Check for and install any available updates to the Wp Cookie Choice plugin via WordPress admin > Plugins > Updates
  2. If no update is available, consider disabling or removing the plugin until a fix is released
  3. Review other plugins from the same developer for similar vulnerabilities

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

Fix this in Wp Cookie Choice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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