VYPR
Unrated severityNVD Advisory· Published Mar 20, 2022· Updated Aug 3, 2024

CVE-2022-26247

CVE-2022-26247

Description

TMS v2.28.0 has an insecure permissions vulnerability in /TMS/admin/user/Update2 allowing any authenticated user to modify the administrator password without authorization.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

TMS v2.28.0 has an insecure permissions vulnerability in /TMS/admin/user/Update2 allowing any authenticated user to modify the administrator password without authorization.

Vulnerability

TMS version 2.28.0 contains an insecure permissions vulnerability in the endpoint /TMS/admin/user/Update2. The component fails to verify that the authenticated user has the right to modify the target account, allowing any logged-in user to change the administrator's password and other details without providing the original password. The vulnerability is triggered via a POST request to /tms/admin/user/update2 with parameters such as username, password, name, and mail [1].

Exploitation

An attacker must have a valid user account on the TMS system and network access to the application. The attacker logs in, navigates to the user modification interface, and intercepts the POST request using a proxy like Burp Suite. By changing the username parameter to admin and setting a new password, the attacker can forward the request to update the administrator account. No verification of the original password is required [1].

Impact

Successful exploitation allows the attacker to change the administrator password and potentially other account details, granting full administrative privileges. This leads to complete compromise of the TMS system, including unauthorized access to sensitive data, modification of system configurations, and potential denial of service [1].

Mitigation

As of the publication date, no official patch has been released by the vendor. Users should restrict network access to the TMS admin interface to trusted IPs, implement additional authentication checks (e.g., require original password for account changes), and monitor for any updates from the vendor. The CVE is not listed in the Known Exploited Vulnerabilities catalog [1].

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.