PerfmattersWordPress extension
CVE-2023-47877
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 Stored XSS.This issue affects Perfmatters: from n/a before 2.2.0.
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 confidenceA stored cross-site scripting (XSS) vulnerability in the Perfmatters WordPress plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. This payload persists in the database and executes when administrative users view affected pages within the plugin settings.
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.2.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check Perfmatters plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Perfmatters and view the version number, or check the plugin header in the main plugin fileAffected if Installed version is below 2.2.0
-
Verify authentication requirementsReview WordPress user roles and confirm whether non-administrator users have access to Perfmatters plugin settings (plugin settings typically require admin privileges)Affected if Authenticated users with access to plugin settings exist in the environment
-
Inspect plugin settings for suspicious contentNavigate to Perfmatters plugin settings pages (Scripts, Extras, Analytics, etc.) and examine input fields for unexpected script tags, event handlers, or encoded JavaScriptAffected if Any input fields contain unescaped HTML or JavaScript code such as <script> tags or javascript: URLs
-
Check database for stored XSS payloadsQuery the WordPress database options table for perfmatters-related settings and inspect values for potential XSS payloads (look for <script, onerror, onload, javascript: patterns)Affected if Database contains HTML or script content in Perfmatters option values that was not entered by a trusted administrator
Environment is affected if Perfmatters version is below 2.2.0 and any unauthenticated or lower-privilege authenticated user can access plugin settings where malicious scripts may be stored.
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 · scoped2.2.0
Update Perfmatters to version 2.2.0 or later to obtain the patched version that properly sanitizes user input. If immediate update is not possible, review user roles and permissions to limit who can access plugin settings.
2.2.0
- Backup your WordPress site database and files
- Update Perfmatters plugin to version 2.2.0 or later through the WordPress admin dashboard (Plugins > Perfmatters > Update)
- Verify the update was successful by checking the plugin version
- Clear any site caches to ensure the new version is served
- Test that the plugin functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Perfmatters
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47877 — 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-47877 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