Telos Automated Message Handling System reflected XSS in LDAP cbURL parameter
Description
Cross-site scripting in Telos AMHS LDAP cbURL parameter allows remote attackers to inject arbitrary script into AMHS sessions; fixed in version 4.1.5.5.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Cross-site scripting in Telos AMHS LDAP cbURL parameter allows remote attackers to inject arbitrary script into AMHS sessions; fixed in version 4.1.5.5.
Vulnerability
The Telos Automated Message Handling System (AMHS) versions prior to 4.1.5.5 contain a cross-site scripting (XSS) vulnerability in the cbURL parameter of the LDAP functionality. The application fails to properly neutralize user input during web page generation, allowing an attacker to inject arbitrary script into an AMHS session [1].
Exploitation
An unauthenticated remote attacker can exploit this vulnerability by crafting a malicious URI containing JavaScript in the cbURL parameter. The attacker must then trick a victim into clicking the crafted link or visiting the malicious URI while authenticated to the AMHS system. No additional privileges or user interaction beyond the initial click are required [1].
Impact
Successful exploitation allows the attacker to execute arbitrary JavaScript in the context of the victim's AMHS session. This can lead to session hijacking, unauthorized actions on behalf of the victim, and disclosure of sensitive information about other AMHS users. The CVSS base score is 6.4 (AV:N/AC:L/Au:N/C:P/I:P/A:N), indicating partial confidentiality and integrity impact [1].
Mitigation
The vulnerability is addressed in AMHS version 4.1.5.5. Users should contact Telos to obtain the update. No workarounds are documented in the available references [1].
AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2<4.1.5.5+ 1 more
- (no CPE)range: <4.1.5.5
- (no CPE)range: unspecified
Patches
0No 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- www.kb.cert.org/vuls/id/873161/mitrethird-party-advisoryx_refsource_CERT-VN
News mentions
0No linked articles in our index yet.