dbcve.org
Performance LabWordPress extension · WordPress

CVE-2022-47174

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 2.2.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 WordPress Performance Team Performance Lab plugin <= 2.2.0 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Performance Lab plugin versions 2.2.0 and below allows attackers to induce authenticated users to perform unintended administrative actions.

MitigationUpdate the Performance Lab plugin to a version newer than 2.2.0, or disable the plugin if no patched version is available.

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
Performance LabWordPress extension
Affected:<= 2.2.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 Performance Lab plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Performance Lab' in the list. Alternatively, check the /wp-content/plugins/ directory for the performance-lab folder.
    Affected if The plugin is not installed or not present in the WordPress environment
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on 'View details' for the Performance Lab plugin, or inspect the main plugin file (usually performance-lab.php) to find the 'Version' header comment.
    Affected if The version displayed is 2.2.0 or lower
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that Performance Lab shows as 'Active' under the plugin status column.
    Affected if The plugin is active and running
  4. Verify authenticated admin access exists
    CSRF attacks require an authenticated administrator to unknowingly submit a malicious request. Confirm whether administrator accounts exist and can access the WordPress admin area.
    Affected if Authenticated administrator sessions are present in the environment

You are affected if the Performance Lab plugin is installed, active, and running version 2.2.0 or lower, with authenticated administrator sessions that could be targeted by CSRF attacks.

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.

From vendor data
Upgrade available Upgrade to a release after 2.2.0
Interim mitigation

Update the Performance Lab plugin to a version newer than 2.2.0, or disable the plugin if no patched version is available.

Fix this in Performance Lab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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