PerfmattersWordPress extension
CVE-2023-47875
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Perfmatters allows Cross Site Request Forgery.This issue affects Perfmatters: from n/a through 2.1.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Perfmatters WordPress plugin up to version 2.1.6 allows attackers to trick authenticated users into performing unintended actions. The vulnerability stems from missing or improper CSRF protection mechanisms in the plugin's admin functionality.
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
PerfmattersWordPress extension
<= 2.1.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Perfmatters plugin is installedNavigate to WordPress admin dashboard > Plugins and verify Perfmatters is listed and active, or inspect the plugin directory at wp-content/plugins/perfmatters/Affected if Plugin is installed and active with version <= 2.1.6
-
Check installed Perfmatters versionView the plugin version in the WordPress plugin list, or open the main plugin file (perfmatters.php) and look for the version header comment, or check readme.txt for the 'Stable tag' entryAffected if Version number returned is 2.1.6 or lower
-
Inspect admin action handlers for missing nonce validationExamine the main plugin PHP file and any admin-related files for state-changing actions (form submissions, settings updates, option changes). Search for the absence of 'wp_verify_nonce' or 'check_admin_referer' calls before performing actions, or verify that action functions do not receive or validate a nonce tokenAffected if Admin actions lack nonce verification logic and the plugin version is <= 2.1.6
Environment is affected if Perfmatters plugin version 2.1.6 or lower is active and admin actions lack WordPress nonce validation checks.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement anti-CSRF tokens (WordPress nonces) on all state-changing admin actions and validate the nonce on the server side. Additionally, add SameSite attribute to session cookies and verify Origin/Referer headers for cross-origin requests.
Update Perfmatters to the latest available version (version after 2.1.6)
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find Perfmatters in the plugin list
- Check if an update is available and click 'Update Now' to update to the latest version
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Perfmatters
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-47875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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