Security readout for executives and security teams
Plain-English summary
This is a medium-risk CSRF issue in the WordPress Snap Pixel plugin through version 1.5.7. If the plugin is active, an attacker may be able to trick a legitimate user into making unintended plugin-related changes. Sources do not describe data theft or confirmed active exploitation.
Executive priority
Handle in normal vulnerability remediation cadence unless the plugin is widely deployed on important sites. Prioritize internet-facing, revenue-generating, or highly administered WordPress properties.
Technical view
CVE-2023-45642 is CWE-352 in Hassan Ali Snap Pixel for WordPress <= 1.5.7. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, no confidentiality impact, and low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites running the Snap Pixel plugin at version 1.5.7 or earlier. The source bundle does not identify affected CPEs or hosting-specific exposure.
Exploitation context
The record is not in CISA KEV, and the supplied sources do not claim active exploitation. Exploitation would require user interaction consistent with CSRF, but the sources do not document the exact affected action.
Researcher notes
Evidence is sparse. The public bundle confirms CSRF, version <= 1.5.7, CVSS 5.4, CWE-352, and no KEV listing. It does not describe the vulnerable endpoint, required victim role, proof-of-concept, or fixed version.
Mitigation direction
- Inventory WordPress sites for the Snap Pixel plugin and version.
- If version is <= 1.5.7, check vendor or Patchstack guidance.
- Update to a vendor-confirmed fixed release if available.
- Disable or remove the plugin where it is not required.
- Limit WordPress administrative access to trusted users.
Validation and detection
- Confirm whether Snap Pixel is installed on each WordPress site.
- Record the installed plugin version and compare against <= 1.5.7.
- Review WordPress logs for suspicious plugin settings changes.
- Verify vendor guidance before marking remediation complete.
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-45642 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
- 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
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:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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.