LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3199: MStore API <= 3.9.6 - Cross-Site Request Forgery to Order Title Update

The MStore API plugin for WordPress is vulnerable to Cross-Site Request Forgery due to missing nonce validation on the mstore_update_status_order_title function. This makes it possible for unauthenticated attackers to update status order title via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This WordPress plugin flaw can let an outside attacker change order status title text if they can trick a logged-in administrator into taking an action. The business impact appears limited to integrity of store/admin content, not data theft or outage, based on the supplied CVSS vector.

Executive priority

Treat as a targeted medium-priority WordPress hygiene issue. It is unlikely to justify emergency response alone, but exposed ecommerce sites should patch or disable promptly because administrator-assisted tampering can affect store operations and customer-facing trust.

Technical view

CVE-2023-3199 is a CSRF issue in the MStore API plugin caused by missing nonce validation in mstore_update_status_order_title. The supplied description says unauthenticated attackers could update status order title through a forged request requiring administrator interaction. CVSS is 4.3 with low integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites running MStore API version 3.9.6 or earlier, especially where administrators remain logged in while browsing external content. The source bundle does not provide reliable CPE data.

Exploitation context

The bundle does not show active exploitation, and KEV is false. Exploitation requires user interaction by a site administrator, such as clicking a malicious link, so this is not described as unauthenticated remote takeover.

Researcher notes

The supplied affected-version metadata is inconsistent: the title says versions up to 3.9.6, while the affected block lists version 0 and defaultStatus unaffected. Use Wordfence and WordPress Trac references as primary validation points before broad scoping.

Mitigation direction

  • Upgrade MStore API to a release newer than 3.9.6 after confirming vendor guidance.
  • If no fixed release is available, disable the plugin until guidance is confirmed.
  • Limit WordPress administrator access to trusted users and managed devices.
  • Remind administrators not to open untrusted links while logged into WordPress.

Validation and detection

  • Inventory WordPress sites for the MStore API plugin and installed version.
  • Flag instances running version 3.9.6 or earlier for remediation review.
  • Review WordPress admin activity for unexpected order status title changes.
  • Confirm patched code includes nonce validation for the affected order-title update function.
Prepared
Confidence
medium
Sources
5

Public sources used

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-3199 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
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

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
4Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-3199Attack 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:N

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
inspireuiMStore API – Create Native Android & iOS Apps On The Cloud0unaffected
Weakness

CWE details

CWE-352

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