CVE-2025-36408: Multiple vulnerabilities found in IBM ApplinX.

Published Jan 20, 2026
·
Updated

IBM ApplinX 11.1 is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

Other sources

IBM ApplinX is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.

IBM

Affected Software

3 affected componentsFixes available
IBM ApplinX
IBM ApplinX<=11.1
IBM ApplinX=11.1.0

Remediation

Information

IBM strongly recommends addressing the vulnerabilities now by upgrading IBM ApplinX. Product Version Remediation/Fix IBM ApplinX 11.1 Download and apply the update from Fix Central here .

Event History

Jan 20, 2026
CVE Published
via IBM·12:00 AM
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
CVE Published
via MITRE·03:33 PM
Data Sourced
via MITRE·03:33 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2025-36408?

CVE-2025-36408 has been classified as a high severity vulnerability due to its potential impact on user credentials and application integrity.

2

How do I fix CVE-2025-36408?

To fix CVE-2025-36408, upgrade to IBM ApplinX version 11.1.0.8 or apply the latest available patches as recommended by IBM.

3

Who is affected by CVE-2025-36408?

CVE-2025-36408 affects all authenticated users of IBM ApplinX version 11.1.

4

What kind of attack can CVE-2025-36408 enable?

CVE-2025-36408 can enable attackers to perform stored cross-site scripting (XSS) attacks allowing them to execute arbitrary JavaScript in the browser of the authenticated user.

5

What should I do if I cannot patch for CVE-2025-36408 immediately?

If immediate patching for CVE-2025-36408 is not possible, consider implementing input validation and output encoding to mitigate the risk of XSS attacks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203