Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Firmanet Software ERP allows SQL Injection.
This issue affects ERP: through 22.11.2024.
NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
Security readout for executives and security teams
Plain-English summary
Firmanet Software ERP has a high-severity SQL injection vulnerability affecting releases through 22.11.2024. An attacker may be able to access sensitive data without authentication. The public sources do not name a vendor patch, and note the vendor did not respond to disclosure outreach.
Executive priority
Treat this as a high-priority exposure review if Firmanet Software ERP is used. Prioritize identifying deployments, reducing reachability, and watching for abuse while checking authoritative sources for remediation guidance.
Technical view
CVE-2024-7837 is a CWE-89 SQL injection issue in Firmanet Software ERP. The CVSS 3.1 score is 8.2 with network access, low complexity, no privileges, and no user interaction required. Reported impact is high confidentiality loss, low integrity impact, and no availability impact.
Likely exposure
Exposure is most likely for organizations running Firmanet Software ERP through 22.11.2024, especially where the ERP is reachable from the internet or broad internal networks. The source bundle does not provide affected CPEs or a detailed version matrix.
Exploitation context
The vulnerability is not listed as KEV in the provided bundle, and the sources provided do not state active exploitation. The risk remains significant because the CVSS vector indicates unauthenticated, remote attack conditions.
Researcher notes
Evidence is limited to the CVE record and Turkish government advisory references. No exploit details, patch version, vulnerable parameter, or proof-of-concept status is provided in the bundle. Avoid assuming exploit maturity beyond the CVSS assessment.
Mitigation direction
Check Firmanet and Turkish government advisories for updated vendor guidance or fixed versions.
Restrict ERP access to trusted networks, VPNs, or allowlisted administrative paths.
Review web application firewall rules for generic SQL injection detection.
Reduce database account privileges used by the ERP where operationally feasible.
Increase monitoring for anomalous ERP requests and database error patterns.
Validation and detection
Inventory all Firmanet Software ERP deployments and externally exposed instances.
Confirm each instance version and whether it is through 22.11.2024.
Review ERP and database logs for suspicious requests or unexpected SQL errors.
Verify compensating controls limit unauthenticated access to ERP entry points.
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.