Security readout for executives and security teams
Plain-English summary
CVE-2023-3209 affects the MStore API WordPress plugin before 3.9.7. The plugin did not properly protect many AJAX actions, allowing settings changes through cross-site request forgery if a legitimate user was induced to trigger a request.
Executive priority
Treat this as a near-term WordPress plugin hygiene issue. Prioritize internet-facing or business-critical stores, especially where plugin settings could affect payments, customer flows, or mobile commerce behavior.
Technical view
The issue is CWE-352 CSRF. The source description says most AJAX actions lacked privilege checks, nonce checks, or both. This could allow unauthorized settings updates in vulnerable MStore API plugin installations before version 3.9.7.
Likely exposure
Exposure is limited to WordPress sites running the MStore API plugin before 3.9.7. The provided metadata does not identify specific hosting patterns, exploit prerequisites, or affected configuration states.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. WPScan is cited as a vulnerability entry with an exploit tag, but the bundle does not provide exploitation details.
Researcher notes
Evidence is concise but incomplete. The core issue is missing authorization and CSRF protections across AJAX actions. No CVSS, detailed affected-version range, or confirmed exploitation evidence is provided beyond the WPScan reference and the “before 3.9.7” description.
Mitigation direction
- Upgrade MStore API to version 3.9.7 or later.
- Check WPScan and vendor guidance for any additional remediation notes.
- Temporarily disable the plugin if updating cannot be completed promptly.
- Review recent settings changes for unauthorized or unexpected modifications.
Validation and detection
- Inventory WordPress sites for the MStore API plugin.
- Confirm installed plugin versions are 3.9.7 or later.
- Review administrative audit logs for suspicious settings updates.
- Verify exposed AJAX actions enforce nonce and privilege checks where review is feasible.
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-3209 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/970735f1-24bb-441c-89b6-5a0959246d6cCVE reference · exploit, vdb-entry
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.