Security readout for executives and security teams
Plain-English summary
Nikstore Core for WordPress is reported vulnerable to unauthenticated SQL injection through version 1.5. An internet attacker may reach the flaw without credentials or user interaction, potentially exposing database information and causing limited service disruption. The supplied sources do not establish active exploitation or identify a confirmed patched version.
Executive priority
Treat this as an immediate inventory and containment priority for internet-facing WordPress assets. Credential-free reachability and possible database disclosure create substantial business risk. Escalate confirmed installations promptly, but avoid claiming compromise without evidence. Obtain authoritative vendor guidance because the supplied sources do not name a fixed version.
Technical view
CVE-2026-73388 is classified as CWE-89 with CVSS 3.1 score 9.3. The vector indicates remote, low-complexity exploitation requiring no privileges or interaction, with high confidentiality impact, no stated integrity impact, limited availability impact, and changed scope. The affected-version metadata is inconsistent with the description.
Likely exposure
WordPress sites running Nikstore Core version 1.5 or earlier are potentially exposed, especially when publicly reachable. Actual exposure depends on plugin presence, version, and vulnerable functionality. The bundle provides no endpoint, configuration prerequisite, deployment prevalence, or reliable CPE data.
Exploitation context
The vulnerability is described as unauthenticated SQL injection and is not listed in KEV. No supplied source confirms active exploitation, public proof-of-concept availability, or observed attacks. Its remote, credential-free characteristics nevertheless justify urgent defensive review.
Researcher notes
The description and title specify Nikstore Core through 1.5, but the structured affected entry lists versions as “n/a” with default status “unaffected” and no CPEs. This inconsistency limits version certainty. No vulnerable parameter, route, patch, advisory detail, exploit artifact, or exploitation telemetry is included.
Mitigation direction
- Inventory WordPress sites for Nikstore Core and record installed versions.
- Check TeconceTheme and Patchstack guidance for a confirmed fixed release or vendor mitigation.
- Disable or remove affected versions where operationally acceptable until authoritative remediation is available.
- Restrict unnecessary public access and monitor affected sites for suspicious database-related activity.
- Back up WordPress files and databases before applying vendor-supported changes.
Validation and detection
- Confirm whether Nikstore Core is installed on every managed WordPress site.
- Verify each installed version against authoritative vendor or Patchstack guidance.
- Confirm affected versions are upgraded, disabled, or removed according to approved remediation.
- Review application, web, and database logs for unusual requests or database errors.
- Validate site functionality and monitoring after remediation without attempting exploitation.
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-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 lookupDatabase 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 lookupCVE-2026-73388 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
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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.
SSVC decision data
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:N/S:C/C:H/I:N/A:L3.94.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/nikstore-core/vulnerability/wordpress-nikstore-core-plugin-1-5-sql-injection-vulnerability?_s_id=cveCVE reference, Patchstack · 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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.