CVE-2025-41013

CVE-2025-41013 is a critical-severity vulnerability in Tcman Gim with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.

Key facts

Description

SQL injection vulnerability in TCMAN GIM v11 in version 20250304. This vulnerability allows an attacker to retrieve, create, update, and delete databases by sending a GET request using the 'idmant' parameter in '/PC/frmEPIS.aspx'.

Frequently asked questions

What is CVE-2025-41013?
SQL injection vulnerability in TCMAN GIM v11 in version 20250304. This vulnerability allows an attacker to retrieve, create, update, and delete databases by sending a GET request using the 'idmant' parameter in '/PC/frmEPIS.aspx'.
How severe is CVE-2025-41013?
CVE-2025-41013 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-41013 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-41013?
CVE-2025-41013 affects Tcman Gim. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-41013?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-41013 have an EU (EUVD) identifier?
Yes. CVE-2025-41013 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-200247.
When was CVE-2025-41013 published?
CVE-2025-41013 was published on 2025-12-02 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Tcman Gim

All CVEs affecting Tcman Gim →

Other CWE-89 (SQL Injection) vulnerabilities

Browse all CWE-89 (SQL Injection) vulnerabilities →