dbcve.org
GimApplication · Tcman

CVE-2025-41014

HIGH · 7.5 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 2025-04-01 or later.
See remediation →
84/100
Remediation priority · High
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
User Enumeration Vulnerability in TCMAN GIM v11 version 20250304. This vulnerability allows an unauthenticated attacker to determine whether a user exists on the system. The vulnerability is exploitable through the 'pda:username' parameter with 'soapaction GetLastDatePasswordChange' in '/WS/PDAWebService.asmx'.

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

User enumeration vulnerability in TCMAN GIM v11 PDA WebService where an unauthenticated attacker can determine valid usernames by sending requests to /WS/PDAWebService.asmx with the 'pda:username' parameter using the GetLastDatePasswordChange soapaction. The system returns different responses for valid versus invalid usernames, allowing automated enumeration.

MitigationImplement uniform error responses for both valid and invalid usernames to prevent enumeration, and add rate limiting or temporary account lockout on the endpoint to disrupt automated attack attempts.

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
GimApplication
Affected:< 2025-04-01

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
None
Availability
None

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

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. Confirm TCMAN GIM PDA WebService is exposed
    Check if the endpoint /WS/PDAWebService.asmx is accessible on your server by attempting to access it via browser or curl
    Affected if The endpoint responds with a service description or WSDL, indicating the WebService is installed and accessible
  2. Determine installed TCMAN GIM version
    Locate the version information through the TCMAN GIM administrative interface, installation directory, or version file, then compare it to the affected range (versions before 2025-04-01)
    Affected if Installed version is earlier than 2025-04-01
  3. Test user enumeration via GetLastDatePasswordChange
    Send two SOAP requests to /WS/PDAWebService.asmx with the soapaction GetLastDatePasswordChange, using different usernames in the pda:username parameter, and compare the HTTP response status codes and message content
    Affected if The responses differ between valid and invalid usernames, allowing an attacker to determine which usernames are valid in the system
  4. Inspect response differences for username validation
    Examine the SOAP response body or HTTP headers for distinct error messages or timing differences when submitting a known-valid username versus a random-invalid username
    Affected if The system returns distinguishable responses that reveal whether a username exists

Your environment is affected if TCMAN GIM version is before 2025-04-01 AND the /WS/PDAWebService.asmx endpoint returns different responses for valid versus invalid usernames, enabling user enumeration.

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.

dbcve · scoped
Upgrade available Upgrade to 2025-04-01 or later
Fixed in 2025-04-01
Interim mitigation

Implement uniform error responses for both valid and invalid usernames to prevent enumeration, and add rate limiting or temporary account lockout on the endpoint to disrupt automated attack attempts.

Recommended fix Moderate confidence

TCMAN GIM v11 version released on or after 2025-04-01

  1. Identify the current installed version of TCMAN GIM v11 by accessing the application or checking system documentation
  2. Download or obtain TCMAN GIM v11 version released on or after 2025-04-01 from the official vendor (contact TCMAN/GIM vendor directly or visit their support portal)
  3. Before upgrading, perform a complete backup of the current GIM installation including database and configuration files
  4. Stop the GIM application services to ensure a clean upgrade process
  5. Install the updated version (2025-04-01 or later) following vendor-provided upgrade instructions
  6. Restart the GIM services and verify the application is functioning correctly
  7. Test the remediation by attempting to enumerate users through the /WS/PDAWebService.asmx endpoint with the 'pda:username' parameter and 'GetLastDatePasswordChange' soapaction to confirm the vulnerability is patched
Caveat Check vendor release notes for any configuration or compatibility changes between versions; ensure database schema compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gim Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41014 — 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-41014 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