Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
DeliveryInject script into ReferenceOtherParty delivery note field
-
ExploitVictim opens affected delivery note record
-
ExecutionStored JavaScript executes in victim session
-
ImpactPerform actions in victim's context
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 | Requires an authenticated account with privileges to edit delivery notes so the attacker can write a payload into the ReferenceOtherParty field at /Documents/DeliveryNotes/Edit/{id} (PR:L). Exploitation further depends on a second user viewing the affected delivery note record for the stored script to fire (UI:P / passive interaction). Limiting factors: the attacker must already hold valid low-privilege access to the delivery note functionality, a separate victim must open the tampered record, and impact is confined to the victim's browser/session context rather than the server itself. |
| Impact | This is a medium-severity stored XSS (vendor CVSS 4.0 base score 5.1) whose real-world risk is moderate and bounded, not an emergency. 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) tells a coherent story: network-reachable and low-complexity, but it requires existing low-level authenticated access (PR:L) to write the payload and passive interaction from a victim (UI:P) who must view the affected delivery note. Impact is confined to the subsequent (victim browser) system - SC:L/SI:L - with no direct confidentiality, integrity, or availability impact to the vulnerable application itself (VC/VI/VA:N), consistent with session-context script execution rather than server compromise. No EPSS score was supplied, so exploitation probability cannot be quantified from the input. The vulnerability is NOT listed in CISA KEV and the single INCIBE reference is an advisory, not exploit code, so there is no public exploit identified at time of analysis. The vuln.today decision label is 'this_month' - a routine-but-timely remediation signal rather than act_now/emergency. Net: a legitimate issue to patch on a normal cycle, de-prioritized relative to unauthenticated or server-impacting flaws by the authentication and user-interaction prerequisites, but not a false alarm given stored XSS can be used for session-context actions against other users. |
| Exploit ScenarioDerived | An authenticated low-privilege user with access to delivery note editing stores a JavaScript payload in the ReferenceOtherParty field of a delivery note at /Documents/DeliveryNotes/Edit/{id}. When another user - such as a colleague or administrator - later opens that delivery note, the script executes in their browser session, allowing the attacker to alter displayed content or perform actions as the victim. No public exploit code is identified; the only source is the INCIBE advisory. |
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's delivery note editor allows a user who can edit delivery notes to persist JavaScript through the ReferenceOtherParty field on the /Documents/DeliveryNotes/Edit/{id} endpoint, which then executes in the browser of any other user who opens the affected record. The vendor rates it CVSS 4.0 base 5.1 and our assessment scores it CVSS 3.1 6.1 with scope change, reflecting that impact is confined to the victim's browser session (content modification and actions performed as that user) rather than the server. Exploitation requires an authenticated low-privilege account plus a second user viewing the tampered note; no public exploit code or CISA KEV entry was identified at time of analysis, and the priority label is 'this_month' rather than an emergency.
RemediationAI
No vendor-released patch or fixed version is identified in the available data; the INCIBE advisory at https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-am-systems-alo-suite is the tracking source and should be checked for a patched release and upgrade instructions before other measures are relied upon. Until a fix is confirmed, reduce exposure by limiting delivery note edit rights to the smallest set of trusted roles, since the injection requires an authenticated account with access to that endpoint; add server-side output encoding or HTML sanitization for ReferenceOtherParty at render time, which may alter the display of any legitimate markup already stored; and deploy a Content Security Policy that blocks inline and untrusted script, accepting that it can break application functionality that depends on inline JavaScript. Restricting or disabling the free-text ReferenceOtherParty field, or validating it against a strict allowlist, removes the injection vector at the cost of delivery note flexibility. Because payloads are stored, any sanitization or field change must be paired with a review and purge of existing delivery note records, and detection should focus on anomalous script content in the ReferenceOtherParty value rather than on network signatures.
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 flaw is CWE-79 (improper neutralization of input during web page generation) in its stored variant: Alo Suite persists the ReferenceOtherParty value from the delivery note edit form and later renders it into pages served to other users without adequate output encoding, so markup supplied by one user becomes executable script in another user's origin. The CVSS 3.1 scope-change component (S:C) is the key technical detail: the injected script does not escalate on the server but crosses a trust boundary into the victim's session, enabling DOM manipulation and authenticated actions with the victim's privileges. The supplied CPE (cpe:2.3:a:am_system:alo_suite:*:*:*:*:*:*:*:*) carries a wildcard version, so the data confirms the product is affected but gives no granularity on which releases are vulnerable versus fixed, and the exact trigger conditions, filter behavior, and rendering context (HTML body, attribute, or script block) are not described 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 attacker stores the payload (PR:L), a victim must view the record (UI:R); script runs in the victim's browser authority, so scope changes (S:C) with limited C/I 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-108050: ReferenceOtherParty in ‘/Documents/DeliveryNotes/Edit/{id}’;
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 Alo Suite (AM System) lets an authenticated user with access to the mail-template editor
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
EUVD-2026-115799
GHSA-37cc-rw3j-pvqf
NVD
CVE.org
Vulnrichment
Exploit-DB