Skip to main content
VulnerabilityPublished

CVE-2025-62192: Japan Total System GroupSession Free edition · SQL Injection

Affects Japan Total System GroupSession Free editionSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium : upgrade to 5.3.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.3.0
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Japan Total System GroupSession Free edition to 5.3.0.

Affected software

ProductAffectedFixed in
Japan Total System Co.,Ltd. GroupSession Free editionAffected
  • <5.3.0
Fixed in
  • 5.3.0

AI-suggested

  1. Upgrade affected GroupSession products to the fixed versions: Free edition to 5.3.0 or later, byCloud to 5.3.3 or later, and ZION to 5.3.2 or later.
  2. Implement strict input validation and sanitization on all user inputs that interact with SQL queries to prevent injection of malicious code.
  3. Use parameterized queries or prepared statements in the application code to ensure SQL commands are constructed safely.
  4. Enforce strong authentication mechanisms and monitor user access logs to detect anomalous behavior indicative of credential compromise or misuse.
  5. Limit user privileges to the minimum necessary to reduce the impact of any compromised accounts.
  6. Conduct regular security audits and code reviews focusing on injection vulnerabilities.
  7. Employ Web Application Firewalls (WAFs) with SQL Injection detection capabilities as an additional layer of defense.
  8. Educate users about phishing and credential security to reduce the risk of account compromise.
  9. Maintain up-to-date backups of critical data to enable recovery in case of data tampering.

Description

SQL Injection vulnerability exists in GroupSession Free edition prior to ver5.3.0, GroupSession byCloud prior to ver5.3.3, and GroupSession ZION prior to ver5.3.2. If exploited, information stored in the database may be obtained or altered by an authenticated user.

References

Community reviews

Loading reviews…