Categories
CVE-2026-44923 medium CVSS 6.5

SQL Injection in InfoScale VIOM (CVE-2026-44923)

Summary

SQL injection in InfoScale VIOM (CVE-2026-44923). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

SQL injection in InfoScale VIOM before v9.1.3 allows remote attackers to escalate privileges.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called CVE-2026-44923 was discovered in InfoScale VIOM.
In plain terms, it is a flaw that lets attackers send rogue commands to the database.
Severity is Medium (CVSS 6.5/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "InfoScale VIOM CVE-2026-44923".

CVE-2026-44923 (InfoScale VIOM). Severity: Medium / CVSSv3 6.5. Category: CWE-89.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2026-44923) in InfoScale VIOM. In plain words, it is a flaw that lets attackers send rogue commands to the database.

📍 Affected scope

Target versions of InfoScale VIOM (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Exploitation requires specific conditions but can cause real harm if successful.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-89)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details