Quick answers
- Is CVE-2026-108054 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108054 being exploited in the wild.
- How severe is CVE-2026-108054?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- AM System ALO Suite before 26_04_15.03_10.
- Is there a fix for CVE-2026-108054?
- Yes: fixed in ALO Suite 26_04_15.03_10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108054 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-108054?
- Check whether you run AM System ALO Suite at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ALO Suite 26_04_15.03_10
Technical details
Multiple stored XSS flaws (CVE-2026-108050 through CVE-2026-108060) exist due to insufficient input sanitization and output encoding across at least 10 different endpoints in ALO Suite, including delivery notes, articles, files, and employee management. Each vulnerability stems from unsafe handling of user-supplied data in specific form fields that are stored server-side and rendered without HTML escaping. Exploitation requires authenticated access but allows an attacker to execute arbitrary JavaScript in the browser context of any user who views the malicious records, enabling session hijacking, credential theft, or administrative actions.
Affected products
- AM System ALO Suite before 26_04_15.03_10
Timeline
- 2026-11-03: disclosed