dbcve.org
GimApplication · Tcman

CVE-2025-40668

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Incorrect authorization vulnerability in TCMAN's GIM v11. This vulnerability allows an attacker, with low privilege level, to change the password of other users through a POST request using the parameters idUser, PasswordActual, PasswordNew and PasswordNewRepeat in /PC/WebService.aspx/validateChangePassword%C3%B1a. To exploit the vulnerability the PasswordActual parameter must be empty.

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

This is an IDOR (Insecure Direct Object Reference) authorization bypass in TCMAN GIM v11's password change web service. The endpoint at /PC/WebService.aspx/validateChangePassword fails to verify that the authenticated user has permission to change the password for the specified idUser parameter, allowing any low-privilege user to reset other users' passwords by submitting an empty PasswordActual value.

MitigationImplement proper authorization checks ensuring users can only change their own passwords, require non-empty and verified current password via the PasswordActual parameter, and add CSRF protection.

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:= 11.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 version is 11.0
    Locate the installed TCMAN GIM version through the application administrative interface, installation directory, or product documentation. Common locations include the About page, config files in the installation directory, or the web application's version information.
    Affected if The installed version is exactly 11.0 (not a later patched version)
  2. Verify vulnerable endpoint exists
    Check if the web service endpoint /PC/WebService.aspx/validateChangePassword is accessible in the TCMAN GIM installation. This is typically found under the /PC/ path in the web root.
    Affected if The endpoint responds to requests, indicating the password change web service is present in the deployment
  3. Check web service authentication configuration
    Review the authentication and session management configuration for the /PC/WebService.aspx endpoint. Determine if the web service validates user session tokens and enforces proper authorization before processing password change requests.
    Affected if The web service accepts requests without validating that the authenticated user matches the idUser parameter being modified, or allows empty PasswordActual values without verification
  4. Inspect authorization logic for password change operation
    Examine the validateChangePassword web method source code or configuration to determine if it verifies that the requesting user has permission to modify the specified idUser's password. Look for explicit authorization checks linking the authenticated session to the target user.
    Affected if No authorization check exists that ensures the authenticated user can only change their own password, or if low-privilege users can modify other users' passwords

A user is affected if running TCMAN GIM version 11.0 with the /PC/WebService.aspx/validateChangePassword endpoint exposed and lacking proper authorization validation on the idUser parameter.

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 proper authorization checks ensuring users can only change their own passwords, require non-empty and verified current password via the PasswordActual parameter, and add CSRF protection.

Fix this in Gim Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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