PerfmattersWordPress extension
CVE-2023-47876
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Perfmatters allows Reflected XSS.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 · high confidenceReflected XSS vulnerability in Perfmatters WordPress plugin (versions through 2.1.6) allows attackers to inject malicious scripts via unsanitized user input that gets reflected in web pages without proper output encoding.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Perfmatters plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the perfmatters folder, or list installed plugins via WordPress admin under Plugins > Installed PluginsAffected if The perfmatters folder exists in wp-content/plugins/ or the plugin appears in the WordPress plugins list
-
Check installed Perfmatters versionOpen wp-content/plugins/perfmatters/perfmatters.php and locate the 'Version' header in the plugin comment block, or view version in WordPress admin plugin listAffected if Version is 2.1.6 or lower
-
Confirm plugin is activeIn WordPress admin, check that Perfmatters appears in the active plugins list or status shows as activeAffected if Plugin is active and accessible to site visitors
-
Identify exposed parametersReview plugin files (especially in includes/ or src/ directories) for $_GET, $_POST, or $_REQUEST usage without sanitization functions like esc_html(), esc_attr(), or sanitize_text_field()Affected if User-supplied input from URL parameters or forms is reflected in output without encoding
If Perfmatters version 2.1.6 or lower is installed, active, and accessible via web requests, the environment is affected by this reflected XSS vulnerability.
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 · scopedUpdate Perfmatters to the latest version to apply the security patch; validate that the update does not conflict with existing site functionality.
Perfmatters 2.1.7 or later
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find Perfmatters in the plugin list
- If an update is available, click 'Update Now' to update to the latest version
- Alternatively, you can manually download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
- After updating, verify the plugin is running version 2.1.7 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Perfmatters
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47876 — 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-47876 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