Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Alo Suite with low-privilege account
-
DeliveryStore JavaScript payload in 'Nombre' field at /PlantillasMail/Edit
-
ExploitVictim user views affected delivery-note record
-
ExecutionScript executes in victim's browser session
-
ImpactPerform actions as victim / alter displayed content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account (PR:L) with access to the mail-template editing functionality at /PlantillasMail/Edit, where the attacker injects a payload into the 'Nombre' field. The stored payload only triggers when a second user views the affected delivery-note records (UI:P / passive interaction), so exploitation depends on a victim opening the poisoned record. Limiting factors: the attacker needs valid credentials and access to the vulnerable feature, impact is confined to the victim's authenticated browser session (no server-side confidentiality/integrity/availability impact), and no unauthenticated or default-configuration path exists. |
| Impact | This is a medium-severity stored XSS (vendor CVSS 4.0 base 5.1) that is a routine-priority item rather than an urgent threat. The vuln.today decision label is 'this_month', not act_now or emergency, which aligns with the signal picture: no CISA KEV listing, no EPSS score supplied, and no public exploit identified at time of analysis - the only reference is the INCIBE coordinated advisory, not proof-of-concept code. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N) is internally consistent with a stored XSS: network-reachable, low complexity, but requiring low-privilege authentication (PR:L) and passive victim interaction (UI:P), with impact confined to the subsequent system (the victim's browser session, SC:L/SI:L) and no direct confidentiality/integrity/availability loss on the vulnerable server itself. No EPSS or KEV data was provided, so probabilistic exploitation likelihood cannot be stated; absence of those signals is not evidence of safety but does mean nothing here elevates this above normal patch cadence. Net: a genuine but contained issue - authenticated stored XSS in a niche business-management product - appropriately triaged as scheduled remediation. |
| Exploit ScenarioDerived | An authenticated low-privilege user with access to the mail-template editing feature stores a JavaScript payload in the 'Nombre' field at /PlantillasMail/Edit. When another user (e.g. an operator viewing the associated delivery-note records) opens the affected record, the script executes in their browser session, allowing the attacker to alter displayed content or perform actions as the victim. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Stored cross-site scripting in Alo Suite (AM System) lets an authenticated user with access to the mail-template editor inject JavaScript through the 'Nombre' field at /PlantillasMail/Edit; the payload is persisted and then executes in the browser of another user who views the affected delivery-note records, allowing the attacker to alter displayed content and act within the victim's session. The vendor rates it CVSS 4.0 base 5.1, and the assessed impact is confined to the victim's session (S:C/C:L/I:L, no server-side confidentiality, integrity or availability impact). No public exploit was identified at time of analysis and there is no KEV listing; priority is routine (this_month).
RemediationAI
No vendor-released patch identified at time of analysis; the INCIBE-CERT advisory at https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-am-systems-alo-suite is the authoritative source for the corrected build once AM System publishes it, and because the CPE carries a wildcard version, no Alo Suite release can be assumed fixed until the vendor states so. Until a patched version is confirmed, the most directly effective compensating control is to restrict access to /PlantillasMail/Edit to the small set of accounts that genuinely perform mail-template administration, which reduces the population able to write into the vulnerable 'Nombre' field - the trade-off is that template maintenance must be centralized on those accounts rather than delegated. In addition, apply output encoding/sanitization to the 'Nombre' field at render time so stored values cannot be interpreted as markup, and deploy a Content-Security-Policy that disallows inline and third-party script: this limits execution of any already-stored payload in victims' browsers, but it does not remove the stored data, requires testing against the application's legitimate front-end scripts, and may break existing template rendering behavior.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a persistent (stored) cross-site scripting flaw, CWE-79, in a web application endpoint rather than a memory-safety or injection-into-backend defect: the 'Nombre' field handled by /PlantillasMail/Edit is insufficiently sanitized on input and insufficiently encoded on output, so script content is saved with the record and rendered into other users' browsers when the affected delivery-note records are opened. The CPE entry cpe:2.3:a:am_system:alo_suite:*:*:*:*:*:*:*:* carries a wildcard version, so no specific release range has been published by the source and all Alo Suite builds should be presumed affected until AM System confirms otherwise. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N) is consistent with the assessed conditions: no attack requirements beyond a normal request, a low-privileged authenticated account is needed, the victim's interaction is passive (viewing the poisoned record), and the measurable impact falls on the subsequent system - the victim's browser session - at low confidentiality and integrity, with no impact on the vulnerable system itself. Because the script runs same-origin in the victim's authenticated context, the payload can rewrite page content and submit actions as that user; the specific injection and render path beyond the 'Nombre' field at /PlantillasMail/Edit is not further detailed in the available sources.
Know when Alo Suite gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Authenticated low-privilege attacker (PR:L) stores the payload but a victim must view it (UI:R); scope changes to the victim's session (S:C) with limited confidentiality/integrity impact and no availability impact.
Primary rating from Vendor (INCIBE).
CVSS VectorVendor: INCIBE
DescriptionCVE.org
A stored Cross-Site Scripting (XSS) vulnerability in Alosuite that affects the delivery note functionality. Insufficient sanitization and encoding of the specified fields allow JavaScript to be stored, which executes in other users’ browsers when they view the affected records. Exploitation requires authenticated access to the affected functionality. The code can alter the displayed content and perform actions within the context of the victim’s session. The list of features, parameters, and endpoints is as follows:
CVE-2026-108058: Nombre in ‘/PlantillasMail/Edit’;
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Alo Suite's user-invitation workflow can assign administrative privileges to a newly invited account because the '/Reque
Alo Suite's password recovery endpoint '/Account/resetPwd' lacks rate and frequency limits, so remote attackers can repe
Unauthenticated information disclosure in AM Systems Alo Suite allows remote attackers to read records belonging to othe
Stored cross-site scripting in AM System's Alo Suite lets an authenticated user persist JavaScript through the 'Nombre'
Stored cross-site scripting in AM System Alo Suite's delivery-note functionality allows an authenticated user to persist
Stored cross-site scripting in AM System's Alo Suite lets an authenticated user persist JavaScript through the 'Nombre'
Stored cross-site scripting (CWE-79) in AM System Alo Suite lets an authenticated, low-privileged user persist JavaScrip
Stored cross-site scripting in Alo Suite lets an authenticated user with access to /Inmuebles/Create persist JavaScript
Stored cross-site scripting (CWE-79) in AM System's Alo Suite lets an authenticated low-privilege user plant JavaScript
Stored cross-site scripting in AM System's Alo Suite lets authenticated users with access to the current-accounts creati
Stored cross-site scripting in AM Systems Alo Suite lets an authenticated user with write access to the 'Codigo' field o
Stored cross-site scripting in Alo Suite lets authenticated users with article or delivery-note creation rights inject J
EUVD-2026-115807
GHSA-cfpm-8433-2hj6
NVD
CVE.org
Vulnrichment
Exploit-DB