Mstore Api - Security Vulnerability (CVE-2023-3209)
CVE-2023-3209
The MStore API WordPress plugin before 3.9.7 does not secure most of its AJAX actions by implementing privilege checks, nonce checks, or a combination of both.
CVE-2023-3209
CVE-2023-3209
The MStore API WordPress plugin before 3.9.7 does not secure most of its AJAX actions by implementing privilege checks, nonce checks, or a combination of both.
CVE-2023-3209
Machine-generated threat intelligence
AI Updated 218 days ago
AI enriched 218 days ago (2026-04-09 06:36 UTC)
The MStore API WordPress plugin before 3.9.7 does not secure most of its AJAX actions by implementing privilege checks, nonce checks, or a combination of both.
Severity is LOW (CVSS 3.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability is assessed as Low based on severity and technical exposure profile.
Primary risk drivers: severity and technical exposure profile
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.
Low priority Contained impact, or it needs privileges an attacker would rarely already hold.
Update Mstore Api to 3.9.7 or later.
That is the complete fix. Everything below is what protects you in the meantime.
No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.
Scan your site to see whether it runs Mstore Api, and at which version.
Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.
You are affected if your site runs Mstore Api. Versions below 3.9.7 are vulnerable; that release and later are not.
Update Mstore Api to version 3.9.7 or later. That is the complete fix.