CVE-2024-8972: SQLi in Mobil365 Informatics' Saha365 App
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Mobil365 Informatics Saha365 App allows SQL Injection.
This issue affects Saha365 App: before 30.09.2024.
Security readout for executives and security teams
Plain-English summary
CVE-2024-8972 is a critical SQL injection issue in Mobil365 Informatics' Saha365 App before 30.09.2024. A remote unauthenticated attacker could potentially affect confidentiality, integrity, and availability. The sources do not show active exploitation or detailed exploit evidence.
Executive priority
Prioritize within the critical patch queue for any confirmed Saha365 deployment. Business risk is potentially severe because the vulnerability class can compromise sensitive records and service availability. Urgency depends on whether the application is deployed, internet-facing, and pre-30.09.2024.
Technical view
The CVE describes CWE-89 improper neutralization in SQL commands affecting Saha365 App releases before 30.09.2024. CVSS 3.1 is 9.8: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to organizations running Mobil365 Informatics Saha365 App before 30.09.2024. The source bundle does not provide CPEs, deployment patterns, component names, or precise vulnerable version ranges beyond that date boundary.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and the cited sources do not state active exploitation. Treat this as high urgency because SQL injection can expose or alter database-backed application data, but do not assume exploitation without additional evidence.
Researcher notes
Available evidence is sparse: no CPEs, no exploit narrative, and one advisory URL is tagged broken in the bundle. Focus research on confirming product presence, exact build lineage, reachable attack surface, and vendor-fixed release details before making exposure claims.
Mitigation direction
Inventory all Saha365 App deployments and identify versions before 30.09.2024.
Upgrade to 30.09.2024 or later where vendor guidance confirms remediation.
Check Mobil365 or government advisory guidance for exact remediation instructions.
Restrict external access to affected instances until remediation is confirmed.
Increase monitoring for database errors, anomalous queries, and unexpected authentication activity.
Validation and detection
Confirm each instance version or release date against the 30.09.2024 boundary.
Review exposed routes and internet-facing access paths for Saha365 App.
Check application and database logs for suspicious SQL errors or abnormal data access.
Verify compensating controls do not replace the required vendor remediation.
Track CVE and advisory updates because source detail is limited.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
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.