dbcve.org
Mta Maita Training SystemApplication · Llisoft

CVE-2025-5170

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability classified as critical was found in llisoft MTA Maita Training System 4.5. This vulnerability affects the function AdminShitiListRequestVo of the file com\llisoft\controller\admin\shiti\AdminShitiController.java. The manipulation of the argument stTypeIds leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in llisoft MTA Maita Training System 4.5's AdminShitiController.java allows remote attackers to inject malicious SQL via the stTypeIds parameter in the AdminShitiListRequestVo function. The vulnerability has a critical CVSS score of 9.8 and public exploits are available.

MitigationImplement parameterized queries or prepared statements for the AdminShitiListRequestVo function to sanitize the stTypeIds parameter before executing database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mta Maita Training SystemApplication
Affected:= 4.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Llisoft MTA Maita Training System is installed
    Locate the application installation directory or check running services for the product. Common locations may include webapp directories or application servers hosting this training system.
    Affected if The product is present on the system
  2. Verify the installed version is 4.5
    Check the application's version information - this may be in a version file, about page, manifest, or configuration file within the installation directory. Compare your found version against the affected range (only version 4.5 is vulnerable).
    Affected if The installed version is exactly 4.5
  3. Confirm AdminShitiController.java is present
    Search the application deployment for the file AdminShitiController.java or its compiled class file. This is the vulnerable component containing the SQL injection flaw.
    Affected if The AdminShitiController component exists in the deployment
  4. Check if the AdminShitiListRequestVo function is accessible
    Identify if the web endpoint or API corresponding to AdminShitiListRequestVo is exposed. This function handles the stTypeIds parameter. Review application routing or endpoint mappings.
    Affected if The AdminShitiListRequestVo function is accessible via web request
  5. Inspect the stTypeIds parameter handling
    If logs or source code are available, examine how the stTypeIds parameter is processed in the AdminShitiListRequestVo function. Look for direct string concatenation in SQL queries without parameterized queries.
    Affected if The stTypeIds parameter is used in SQL queries without sanitization or prepared statements

A user is affected only if they have Llisoft MTA Maita Training System version 4.5 installed AND the AdminShitiListRequestVo function with the stTypeIds parameter is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for the AdminShitiListRequestVo function to sanitize the stTypeIds parameter before executing database queries.

Fix this in Mta Maita Training System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5170 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data