LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47875: WordPress Perfmatters Plugin <= 2.1.6 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Perfmatters allows Cross Site Request Forgery.This issue affects Perfmatters: from n/a through 2.1.6.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Perfmatters for WordPress through version 2.1.6 has a CSRF flaw. If a site user with relevant permissions is tricked into interacting with malicious content, unintended plugin-related changes may occur. The public record rates this medium severity, with limited integrity and availability impact and no confidentiality impact stated.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not documented as actively exploited here, but exposed sites should be inventoried and updated through normal vulnerability management because CSRF can cause unauthorized operational changes.

Technical view

CVE-2023-47875 is CWE-352 in the WordPress Perfmatters plugin through 2.1.6. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity impact, and low availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running the Perfmatters plugin at version 2.1.6 or earlier. The source bundle does not provide CPEs, affected actions, or a fixed version.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. CVSS indicates exploitation requires user interaction, consistent with a CSRF scenario where a victim is induced to trigger an unwanted request.

Researcher notes

Evidence is thin beyond the CVE and Patchstack entry. The bundle confirms affected range through 2.1.6, CWE-352, and CVSS vector, but not vulnerable endpoints, nonce coverage, role requirements, proof-of-concept details, or fixed release metadata.

Mitigation direction

  • Inventory WordPress sites using the Perfmatters plugin.
  • Check installed Perfmatters versions and flag 2.1.6 or earlier.
  • Review Perfmatters or Patchstack guidance for the fixed version.
  • Update the plugin if vendor guidance identifies a corrected release.
  • Restrict administrative access until vulnerable installations are addressed.

Validation and detection

  • Confirm whether Perfmatters is installed on each WordPress site.
  • Record the exact plugin version from WordPress inventory.
  • Verify remediation against vendor or Patchstack advisory details.
  • Review logs for unexpected plugin-setting changes around exposure windows.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47875 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-47875Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PerfmattersPerfmattersn/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.