Security readout for executives and security teams
Plain-English summary
This issue affects the WordPress MainWP Matomo Extension at version 4.0.4 or earlier. A successful CSRF attack could trick an authenticated administrator into changing plugin settings. The published impact is limited to integrity, not data theft or service outage.
Executive priority
Handle through normal medium-severity remediation timelines, but prioritize environments where WordPress administration is broadly delegated or the extension controls important analytics settings.
Technical view
CVE-2023-23659 is a CWE-352 CSRF vulnerability in MainWP Matomo Extension <= 4.0.4. CVSS 3.1 is 4.3 with network access, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact.
Likely exposure
Exposure is limited to WordPress sites running MainWP Matomo Extension version 4.0.4 or earlier. The source bundle does not identify CPEs or additional affected products.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. Exploitation requires user interaction, likely involving an authenticated administrator being induced to perform a request.
Researcher notes
The available record describes CSRF leading to plugin settings change, but does not include proof of active exploitation, fixed version details, CPEs, or detailed affected-version ranges beyond <= 4.0.4.
Mitigation direction
- Inventory WordPress sites for MainWP Matomo Extension usage.
- Check MainWP and Patchstack guidance for a fixed version or vendor mitigation.
- Update the extension if a vendor-supported fixed release is available.
- Disable or remove the extension where it is not required.
- Limit administrator browsing exposure until remediation is confirmed.
Validation and detection
- Confirm whether the extension is installed on each WordPress site.
- Record installed versions and flag version 4.0.4 or earlier.
- Review plugin settings for unexpected or unauthorized changes.
- Verify vendor or Patchstack notes before closing remediation.
- Document affected systems, remediation status, and residual uncertainty.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2023-23659 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (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:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.