LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45055: WordPress MStore API Plugin <= 4.0.6 is vulnerable to SQL Injection

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InspireUI MStore API allows SQL Injection.This issue affects MStore API: from n/a through 4.0.6.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-45055 is a critical SQL injection flaw in the InspireUI MStore API WordPress plugin through version 4.0.6. An unauthenticated remote attacker may be able to affect database confidentiality, integrity, and availability. Treat exposed WordPress sites using this plugin as urgent until version status and vendor guidance are confirmed.

Executive priority

Prioritize this as urgent for any internet-facing WordPress site using MStore API through 4.0.6. The main decision is whether to update, disable, or remove the plugin until trusted vendor remediation is confirmed.

Technical view

The CVE describes CWE-89 improper neutralization in SQL commands affecting MStore API through 4.0.6. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, and no user interaction. The supplied sources do not identify the vulnerable parameter, endpoint, exploit details, or fixed version.

Likely exposure

Exposure is limited to WordPress sites with the InspireUI MStore API plugin installed and enabled at version 4.0.6 or earlier. Publicly reachable WordPress deployments carry the highest business risk because the CVSS vector requires only network access.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is still high because the vulnerability is unauthenticated, remotely reachable, and scored for high confidentiality, integrity, and availability impact.

Researcher notes

The public bundle establishes product, affected version range, CWE, and CVSS severity, but lacks endpoint, parameter, patch version, and exploitation telemetry. Avoid assumptions beyond MStore API through 4.0.6 unless vendor or Patchstack details confirm them.

Mitigation direction

  • Inventory all WordPress sites for MStore API plugin installations.
  • Identify any installed MStore API version 4.0.6 or earlier.
  • Check InspireUI and Patchstack guidance for a patched version or workaround.
  • Update to a vendor-supported fixed release if available.
  • Disable or remove the plugin where no safe fixed version is confirmed.
  • Monitor WordPress, database, and WAF logs for SQL error patterns.

Validation and detection

  • Confirm plugin name and version from WordPress administration or asset inventory.
  • Verify whether affected sites are publicly reachable.
  • Recheck vendor and Patchstack advisories for remediation status.
  • After remediation, confirm the vulnerable plugin version is absent.
  • Review recent database and application logs for suspicious errors or unexpected changes.
Prepared
Confidence
medium
Sources
3

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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-45055 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
2Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-45055Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

Products and packages named in the record

VendorProductVersion / packageStatus
InspireUIMStore APImstore-api, n/aunaffected
Weakness

CWE details

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