LiveActive security incident?Get immediate response
CVE Record

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

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.
Prepared
Confidence
medium
Sources
4

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.

Open ATT&CK lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2024-8972 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-8972Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Mobil365 InformaticsSaha365 App0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.