Security readout for executives and security teams
Plain-English summary
Super Store Finder for WordPress is reported vulnerable to unauthenticated SQL injection through version 7.8. An internet-based attacker could target a vulnerable site without credentials or user interaction, potentially exposing database information and disrupting service. The supplied sources do not document confirmed exploitation or a specific fixed release.
Executive priority
Prioritize immediate inventory and exposure reduction for public WordPress sites. The reported attack conditions and potential confidentiality impact justify urgent action, even without confirmed exploitation. Require owners to verify remediation against authoritative guidance and investigate exposed systems for suspicious activity.
Technical view
CVE-2026-73392 is classified as CWE-89 with CVSS 3.1 score 9.3. Its vector indicates network access, low complexity, no privileges, no interaction, changed scope, high confidentiality impact, no integrity impact, and low availability impact. The bundle does not identify the vulnerable parameter, endpoint, or remediation version.
Likely exposure
WordPress sites using Super Store Finder version 7.8 or earlier may be exposed, particularly where affected plugin functionality is publicly reachable. The structured affected-version record is incomplete and lists “n/a,” so administrators should verify installed versions and authoritative vendor guidance rather than relying solely on automated CPE matching.
Exploitation context
The vulnerability is remotely reachable and reportedly requires neither authentication nor user interaction. However, it is not listed as a CISA KEV in the supplied bundle, and no cited evidence confirms active exploitation. Treat exploit activity as unknown, not established.
Researcher notes
Public evidence supplied here is sparse. It establishes the vulnerability class, affected-version claim, and CVSS vector, but not the vulnerable endpoint, parameter, root cause, proof of exploitation, patch commit, or fixed version. The structured affected entry also lacks a usable version range, reducing confidence in automated exposure determination.
Mitigation direction
- Identify every WordPress site running Super Store Finder and record its installed version.
- Check the plugin vendor and Patchstack guidance for a confirmed fixed release or official mitigation.
- Update to a confirmed safe version when authoritative guidance identifies one.
- If no safe version exists, disable the plugin or restrict affected functionality until guidance is available.
- Monitor WordPress and database logs for unusual requests, errors, or unexpected access patterns.
Validation and detection
- Confirm whether Super Store Finder is installed, active, and version 7.8 or earlier.
- Determine whether the plugin’s affected functionality is reachable without authentication.
- Verify the deployed version against current vendor or Patchstack remediation guidance.
- Review relevant web, WordPress, and database logs for suspicious activity around the affected functionality.
- After remediation, confirm the vulnerable version is absent across production, staging, and dormant sites.
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-73392 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/superstorefinder-wp/vulnerability/wordpress-super-store-finder-plugin-7-8-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
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.