Quick answers
- Is CVE-2026-108053 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108053 being exploited in the wild.
- How severe is CVE-2026-108053?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- AM System ALO Suite 25_09_15.03_35 and earlier.
- Is there a fix for CVE-2026-108053?
- Yes: fixed in ALO Suite version 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-108053 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-108053?
- 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 version 26_04_15.03_10
Technical details
The vulnerability is a stored XSS flaw affecting at least 11 endpoints across ALO Suite (CVE-2026-108050 through CVE-2026-108060) where fields including "Nombre", "ReferenceOtherParty", "Codigo", "NombrePF", and "Observaciones" lack proper input sanitization and output encoding. An authenticated attacker can inject malicious scripts into these fields via endpoints such as '/CuentasCorrientes/Create', '/Familias/Edit/{id}', and '/Trabajadores/Create'; when other authenticated users view the stored data, the JavaScript executes in their browser context, allowing session hijacking or unauthorized actions.
Affected products
- AM System ALO Suite 25_09_15.03_35 and earlier
Timeline
- 2026-11-03: disclosed