dbcve.org
Crowdsignal DashboardWordPress extension · Automattic

CVE-2022-45069

HIGH · 8.8 CVSS v3.1 Published 2022-11-17
Fix available
A fix is available. Upgrade to 3.0.10 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Auth. (contributor+) Privilege Escalation vulnerability in Crowdsignal Dashboard plugin <= 3.0.9 on WordPress.

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

An authenticated privilege escalation vulnerability exists in the Crowdsignal Dashboard plugin for WordPress versions 3.0.9 and earlier. Users with contributor-level permissions can exploit insufficient access controls to elevate their privileges to higher administrative roles, bypassing role-based capability checks.

MitigationUpdate the Crowdsignal Dashboard plugin to version 3.0.10 or later. If immediate update is not possible, restrict or disable the plugin until the patch can be applied.

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.0.10

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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
    Go to WordPress admin > Plugins and look for 'Crowdsignal Dashboard' in the installed plugins list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in the active plugins list
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Crowdsignal Dashboard and note the version number displayed under the plugin name, or check via database: SELECT option_value FROM wp_options WHERE option_name = 'Crowdsignal';
    Affected if Version is 3.0.9 or earlier, or if the version cannot be determined but the plugin is present on a WP version predating 3.0.10
  3. Identify users with contributor role
    In WordPress admin > Users, filter by 'Contributor' role to see all users with that permission level, or query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%';
    Affected if Any contributor-level users exist in the system who could potentially exploit this vulnerability
  4. Review recent role changes
    Check WordPress user roles in the database for any unexpected capability additions to lower-privileged roles, or audit user_meta table for changes to wp_capabilities that may indicate privilege escalation attempts
    Affected if Contributor users have acquired administrative capabilities or roles they should not possess

You are affected if the Crowdsignal Dashboard plugin versions 3.0.9 or earlier are installed and active, regardless of whether contributor users have actually exploited the flaw yet.

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.0.10 or later
Fixed in 3.0.10
Interim mitigation

Update the Crowdsignal Dashboard plugin to version 3.0.10 or later. If immediate update is not possible, restrict or disable the plugin until the patch can be applied.

Recommended fix High confidence

3.0.10 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find the Crowdsignal Dashboard plugin
  4. Click 'Update Now' to update to the latest version (3.0.10 or higher)
  5. Alternatively, you can update automatically via WordPress.org plugin repository
  6. After update, verify the installed version is 3.0.10 or higher in the Plugins list
  7. Test that contributor+ users cannot escalate privileges beyond their assigned role

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

Fix this in Crowdsignal Dashboard Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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