Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-57871 Overview
CVE-2025-57871 is a reflected cross-site scripting (XSS) vulnerability in Esri Portal for ArcGIS version 11.4 and earlier. A remote authenticated attacker holding administrative access can supply a crafted string that triggers execution of arbitrary JavaScript in a victim's browser session. The flaw is tracked under CWE-79 (Improper Neutralization of Input During Web Page Generation).
Esri published the fix in the Portal for ArcGIS Security 2025 Update 3 patch. The vulnerability requires both authentication and user interaction, which limits mass exploitation, but admin-privileged XSS can facilitate session takeover and lateral movement within GIS workflows.
Critical Impact
An authenticated administrator with malicious intent, or a compromised admin account, can execute arbitrary JavaScript in another user's browser context, enabling session hijacking, data exfiltration, or further compromise of the ArcGIS portal.
Affected Products
- Esri Portal for ArcGIS 10.9.1 (including Security 2025 Update 1 and Update 2)
- Esri Portal for ArcGIS 11.0, 11.1, 11.2, 11.3 (including all prior security updates)
- Esri Portal for ArcGIS 11.4 (including Security 2025 Update 1 and Update 2)
Discovery Timeline
- 2025-09-29 - CVE-2025-57871 published to the National Vulnerability Database
- 2026-10-09 - Last updated in NVD database
Technical Details for CVE-2025-57871
Vulnerability Analysis
The vulnerability is a reflected cross-site scripting flaw in Portal for ArcGIS, Esri's web-based component for sharing maps, apps, and geospatial content. Reflected XSS occurs when user-supplied input is echoed back into an HTTP response without proper encoding or sanitization. When the response renders in a browser, the attacker-controlled payload executes within the origin of the trusted portal.
Exploitation requires an authenticated session with administrative privileges. The attacker crafts a URL or request that embeds JavaScript into a parameter processed by the portal. When another administrator or user is persuaded to open the crafted link, the payload executes in their browser. The scope is marked as changed in the CVSS vector, which indicates the payload can affect resources beyond the originally vulnerable component — for example, interacting with cookies, tokens, or iframe content from related portal services.
Root Cause
The root cause is improper neutralization of user-controlled input before it is reflected in generated web pages. Specific parameters accepted by portal endpoints are not sufficiently escaped or validated. Any HTML or JavaScript characters placed into those parameters are returned verbatim in the rendered response, allowing the browser to interpret attacker content as executable script within the portal origin.
Attack Vector
The attack chain requires: an attacker with authenticated administrative access to craft the malicious URL or payload; a second user with an active portal session to click or load the crafted link; and the vulnerable endpoint to reflect the payload. Successful exploitation delivers code execution in the victim's browser under the portal domain, from where the attacker can read tokens, perform API actions as the victim, or stage phishing content.
No public proof-of-concept, exploit module, or CISA KEV listing is associated with this CVE at the time of publication. Esri has not released exploitation telemetry.
Detection Methods for CVE-2025-57871
Indicators of Compromise
- Portal access logs containing requests with URL parameters embedding HTML tags, <script>, javascript:, event handler attributes such as onerror= or onload=, or encoded equivalents (%3Cscript%3E).
- Unexpected outbound browser requests from administrator workstations to attacker-controlled domains following administrative portal activity.
- Portal audit entries showing administrative API actions originating from sessions that also loaded suspicious reflected-URL requests.
Detection Strategies
- Inspect web server and reverse proxy logs for query strings and POST bodies on Portal for ArcGIS endpoints that contain scripting syntax or encoded script markers.
- Correlate administrator browser telemetry with portal request logs to identify sessions where a reflected payload was rendered.
- Monitor for anomalous use of administrator session tokens, including API calls from new IP addresses or at unusual times after reflected URLs were loaded.
Monitoring Recommendations
- Enable verbose request logging on Portal for ArcGIS and forward logs to a centralized analytics platform for retention and query.
- Add Web Application Firewall (WAF) rules that alert on reflected-XSS payload patterns in requests to the portal domain.
- Track administrator account activity, especially link-sharing and content-management actions, for behavioral deviations.
How to Mitigate CVE-2025-57871
Immediate Actions Required
- Apply the Portal for ArcGIS Security 2025 Update 3 patch to all affected deployments as outlined in the Esri Security Patch Update.
- Review administrator accounts, enforce multi-factor authentication, and remove unused administrative privileges to shrink the exploitation surface.
- Instruct administrators to avoid opening portal links received from untrusted or unverified sources until patching is complete.
Patch Information
Esri has released the Portal for ArcGIS Security 2025 Update 3 patch, which remediates CVE-2025-57871. The patch is available through the Esri customer portal and documented in the vendor advisory. Organizations running any version from 10.9.1 through 11.4 should install the appropriate update for their deployment baseline.
Workarounds
- Restrict administrative access to Portal for ArcGIS to trusted networks or jump hosts to limit who can both author and receive reflected links.
- Deploy a WAF or reverse proxy rule set that filters requests containing script tags, event-handler attributes, and common XSS encoding patterns targeting portal endpoints.
- Configure a strict Content Security Policy (CSP) header at the reverse proxy where supported, limiting inline script execution within the portal origin.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

