CVE-2025-55104: Esri Portal for ArcGIS Enterprise Sites · Cross-site Scripting
Affects Esri Portal for ArcGIS Enterprise SitesSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Esri Portal for ArcGIS Enterprise Sites | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Restrict site creation and editing privileges strictly to trusted and trained personnel to minimize the risk of malicious payload injection. 2) Implement rigorous input validation and output encoding on all user-supplied content within the portal, especially for fields that allow HTML or script content. 3) Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing the portal. 4) Monitor and audit site content changes regularly for suspicious or unexpected script insertions. 5) Educate users about the risks of XSS and encourage cautious behavior when interacting with portal content. 6) Maintain strict session management and consider implementing HttpOnly and Secure flags on cookies to reduce session hijacking risks. 7) Apply any vendor patches or updates as soon as they become available, and engage with Esri support to obtain interim fixes or workarounds. 8) Consider network segmentation and access controls to limit exposure of the portal to only necessary users and systems. 9) Use web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting the portal.
Description
A stored cross-site scripting (XSS) vulnerability exists ArcGIS HUB and ArcGIS Enterprise Sites which allows an authenticated user with the ability to create or edit a site to add and store an XSS payload. If this stored XSS payload is triggered by any user attacker supplied JavaScript may execute in the victim's browser.