dbcve.org
GimApplication · Tcman

CVE-2025-41012

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 2025-04-01 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Unauthorized access vulnerability in TCMAN GIM v11 version 20250304. This vulnerability allows an unauthenticated attacker to determine whether a user exists on the system by using the 'pda:userId' and 'pda:newPassword' parameters with 'soapaction UnlockUser’ 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 · moderate confidence

Unauthenticated user enumeration vulnerability in TCMAN GIM v11's PDAWebService.asmx endpoint. Attackers can determine valid user accounts by sending SOAP requests with the 'UnlockUser' soapaction and observing different response behaviors for existing versus non-existing user IDs.

MitigationImplement proper authentication checks before the UnlockUser function responds, and ensure uniform error responses that do not reveal user existence. Consider restricting or disabling the PDAWebService.asmx endpoint from unauthenticated access.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify TCMAN GIM installation exists
    Locate the web application directory and confirm the presence of PDAWebService.asmx file, typically found under the application's web services path
    Affected if PDAWebService.asmx file is present in the deployed web application
  2. Check PDAWebService.asmx accessibility
    Attempt to access PDAWebService.asmx from an unauthenticated network location using HTTP GET request
    Affected if The endpoint returns a valid WSDL or service description without requiring authentication
  3. Determine TCMAN GIM version
    Inspect version information in application metadata, configuration files, or headers returned by the web service
    Affected if The installed version predates the 2025-04-01 patch date or version information is unavailable (older deployment)
  4. Test UnlockUser response behavior
    Send SOAP requests to the endpoint with the UnlockUser soapaction: first with a likely valid user ID, then with a random/non-existing ID, and compare HTTP status codes and response messages
    Affected if The responses differ in content, timing, or error messages between existing and non-existing user IDs, revealing user enumeration capability

A defender is affected if PDAWebService.asmx is accessible without authentication and returns different responses for valid versus invalid user IDs in the UnlockUser operation.

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 proper authentication checks before the UnlockUser function responds, and ensure uniform error responses that do not reveal user existence. Consider restricting or disabling the PDAWebService.asmx endpoint from unauthenticated access.

Recommended fix Moderate confidence

GIM v11 version 2025-04-01 or later

  1. 1. Identify the current installed version of TCMAN GIM by checking the application or consulting system documentation.
  2. 2. Download the updated version of TCMAN GIM v11 (version 2025-04-01 or later) from the official vendor (Incibe or TCMAN).
  3. 3. Before applying the update, perform a full backup of the current GIM installation including database and configuration files.
  4. 4. Apply the upgrade following the vendor's documented upgrade procedure.
  5. 5. Verify the fix by attempting to access the /WS/PDAWebService.asmx endpoint without proper authentication and confirming the UnlockUser soapaction no longer reveals user existence information.
  6. 6. Validate that the web service now properly requires authorization for sensitive operations.
Caveat Review vendor release notes for any breaking changes between current version and 2025-04-01; potential configuration or workflow adjustments may be required

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

Fix this in Gim Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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