CVE-2023-51810: SQL injection vulnerability in StackIdeas EasyDiscuss v.5.0.5 and fixed in v.5.0.10 allows a remote attacke...
SQL injection vulnerability in StackIdeas EasyDiscuss v.5.0.5 and fixed in v.5.0.10 allows a remote attacker to obtain sensitive information via a crafted request to the search parameter in the Users module.
Security readout for executives and security teams
Plain-English summary
CVE-2023-51810 is a high-severity SQL injection issue in StackIdeas EasyDiscuss 5.0.5. A remote unauthenticated attacker could use the Users module search parameter to extract sensitive information. The provided record says the issue is fixed in 5.0.10.
Executive priority
Treat this as a near-term remediation item for any internet-facing EasyDiscuss deployment. The main business risk is unauthorized access to sensitive database-backed information, not service disruption.
Technical view
The CVE describes CWE-89 SQL injection reachable over the network with low complexity, no privileges, and no user interaction. CVSS 3.1 is 7.5, driven by high confidentiality impact with no stated integrity or availability impact.
Likely exposure
Organizations running StackIdeas EasyDiscuss version 5.0.5 are the indicated exposure group. Public-facing deployments are more urgent because the attack vector is network-accessible and unauthenticated.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. It does include a public GitHub reference, so defenders should assume vulnerability details may be accessible.
Researcher notes
Evidence is narrow: the CVE states EasyDiscuss 5.0.5 is vulnerable and 5.0.10 fixes it, but structured affected CPE data is unavailable. Avoid expanding scope beyond StackIdeas EasyDiscuss without vendor confirmation.
Mitigation direction
Upgrade EasyDiscuss 5.0.5 to fixed version 5.0.10 or later.
Check StackIdeas guidance for any additional required remediation.
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.