CVE-2018-25371: mooSocial Store Plugin 2.6 SQL Injection via product parameter
mooSocial Store Plugin 2.6 contains a blind SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries through the product parameter in URL rewrite functionality. Attackers can inject SQL code using boolean-based blind, time-based blind, or stacked query techniques in the product URI parameter to extract sensitive database information.
Security readout for executives and security teams
Plain-English summary
CVE-2018-25371 affects mooSocial Store Plugin 2.6. An unauthenticated attacker may be able to abuse a product URL parameter to query the site database indirectly. For affected public sites, the main business risk is exposure of sensitive database data. The source bundle does not show a confirmed vendor patch or active exploitation.
Executive priority
Prioritize this for any public mooSocial Store Plugin 2.6 deployment. The issue is unauthenticated, network reachable, and can threaten database confidentiality. If the plugin is not present or not exposed, urgency drops substantially.
Technical view
The vulnerability is CWE-89 SQL injection in mooSocial Store Plugin 2.6 URL rewrite handling. The product URI parameter is described as injectable using blind SQL injection techniques, including boolean, time-based, and stacked-query variants. CVSS 4.0 is 8.8 with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is likely limited to mooSocial deployments running the Store Plugin version 2.6, especially internet-facing sites with store product URL rewrite functionality enabled. The bundle does not identify affected CPEs, patched versions, or other mooSocial components.
Exploitation context
A public ExploitDB reference is listed, so exploit information exists publicly. However, KEV is false and the provided sources do not establish active exploitation in the wild. Treat this as a credible external attack path for exposed affected sites.
Researcher notes
Evidence is specific on vulnerable component, parameter, class of bug, and attack preconditions. Evidence is incomplete on vendor patch status, affected ranges beyond 2.6, real-world exploitation, and safe detection signatures. Avoid assuming broader mooSocial platform exposure without local confirmation.
Mitigation direction
Inventory mooSocial sites and confirm whether Store Plugin 2.6 is installed.
Check mooSocial vendor guidance for a fixed version or official remediation.
Disable or restrict the Store Plugin if no verified fix is available.
Reduce public exposure for affected store routes where business impact allows.
Review database and web logs for unusual product parameter activity.
Validation and detection
Confirm plugin name and version from administrative or deployment records.
Identify public routes using Store Plugin product URL rewrite handling.
Review WAF, web, and database logs for suspicious SQL error or timing patterns.
Verify whether vendor documentation names a patched version or configuration change.
Track CVE, VulnCheck, and vendor pages for updated remediation details.
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.
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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
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.