dbcve.org
Crowdsignal DashboardWordPress extension · Automattic

CVE-2023-51489

HIGH · 8.8 CVSS v3.1 Published 2024-03-16
Fix available
A fix is available. Upgrade to 3.1.0 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 Automattic, Inc. Crowdsignal Dashboard – Polls, Surveys & more.This issue affects Crowdsignal Dashboard – Polls, Surveys & more: from n/a through 3.0.11.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Crowdsignal Dashboard WordPress plugin (versions through 3.0.11) allows attackers to trick authenticated users into performing unintended actions by leveraging the lack of proper token validation on sensitive requests.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations and validate Origin/Referer headers to ensure requests originate from legitimate sources.

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
Crowdsignal DashboardWordPress extension
Affected:< 3.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
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. Verify Crowdsignal Dashboard plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate the Crowdsignal Dashboard plugin. Note its active/inactive status.
    Affected if Plugin is installed and active
  2. Check installed plugin version
    In the Plugins list, view the plugin details to find the version number. Compare it to the affected range: versions through 3.0.11 (any version < 3.1.0)
    Affected if Installed version is less than 3.1.0
  3. Identify state-changing operations in the plugin
    Review plugin functionality for any actions that modify data: settings changes, user data submissions, form posts, or administrative actions performed via the plugin.
    Affected if The plugin performs any state-changing operations
  4. Check for nonce validation on sensitive requests
    Inspect the code handling the sensitive operations identified. Look for wp_verify_nonce(), check_ajax_referer(), or similar nonce verification calls in the request handlers.
    Affected if Sensitive request handlers lack proper nonce/token validation

User is affected if the Crowdsignal Dashboard plugin is active with version < 3.1.0 and performs state-changing operations without validating 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 3.1.0 or later
Fixed in 3.1.0
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations and validate Origin/Referer headers to ensure requests originate from legitimate sources.

Recommended fix High confidence

3.1.0

  1. 1. Back up your WordPress site and database before proceeding with any updates
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the Crowdsignal Dashboard plugin (also known as Crowdsignal - Polls, Surveys & more)
  5. 5. If an update is available, click 'Update Now' to upgrade to version 3.1.0 or later
  6. 6. Alternatively, download version 3.1.0 from the WordPress plugin repository and upload manually via Plugins > Add New > Upload Plugin
  7. 7. Verify the plugin is running version 3.1.0 or higher after the update

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

Fix this in Crowdsignal Dashboard 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-2023-51489 — 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-2023-51489 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