dbcve.org
GimApplication · Tcman

CVE-2025-41015

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 GetUserQuestionAndAnswer' 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 allows unauthenticated attackers to determine valid usernames through the PDAWebService.asmx endpoint. The GetUserQuestionAndAnswer soap action with the pda:username parameter returns different responses based on whether the username exists, enabling automated username harvesting for subsequent attacks.

MitigationRestrict or require authentication for the /WS/PDAWebService.asmx endpoint, implement rate limiting and account lockout policies, and normalize responses to prevent user existence disclosure.

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. Identify if TCMAN GIM is installed
    Search for TCMAN GIM installation directories or check for related services running on the system. Look for installation paths containing 'TCMAN' or 'GIM' in program files or application directories.
    Affected if TCMAN GIM software is present on the system
  2. Determine installed version of TCMAN GIM
    Check the product version through the application itself, installation logs, or registry entries. Compare the version against the affected range: versions released before April 1, 2025 are vulnerable.
    Affected if Installed version is any release prior to 2025-04-01
  3. Locate the PDAWebService.asmx endpoint
    Check if the web service endpoint is accessible by navigating to /WS/PDAWebService.asmx or /PDAWebService.asmx on the TCMAN GIM web server. Verify the endpoint responds to HTTP requests.
    Affected if The PDAWebService.asmx endpoint is exposed and accessible over the network
  4. Test for user enumeration via GetUserQuestionAndAnswer
    Send a SOAP request to the endpoint with the GetUserQuestionAndAnswer action, providing a test username in the pda:username parameter. Compare responses for valid versus invalid usernames.
    Affected if The endpoint returns measurably different responses (such as error codes, response times, or error messages) that reveal whether a specific username exists in the system

Users are affected if TCMAN GIM version is prior to 2025-04-01 AND the PDAWebService.asmx endpoint is externally accessible and returns distinguishable responses based on username validity.

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

Restrict or require authentication for the /WS/PDAWebService.asmx endpoint, implement rate limiting and account lockout policies, and normalize responses to prevent user existence disclosure.

Recommended fix High confidence

TCMAN GIM v11 version 2025-04-01 or later

  1. 1. Identify the current version of TCMAN GIM v11 installed in the environment
  2. 2. Download TCMAN GIM v11 version 2025-04-01 or later from the official vendor source
  3. 3. Review the vendor's upgrade documentation for v11
  4. 4. Perform a full backup of the current Gim installation including database and configuration files
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade following vendor-provided migration procedures
  7. 7. Verify the upgrade was successful by checking the version number
  8. 8. Confirm the vulnerability is resolved by testing the '/WS/PDAWebService.asmx' endpoint with the 'GetUserQuestionAndAnswer' soapaction
Caveat Review vendor release notes for v11 upgrade; may require database migration or configuration changes

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

Fix this in Gim Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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