Skip to main content
VulnerabilityPublished Updated

CVE-2025-57870: Esri ArcGIS Server · SQL Injection

Affects Esri ArcGIS ServerSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Esri ArcGIS ServerAffected
  • =11.3
  • =11.4
  • =11.5
Fixed in–

AI-suggested

  1. Immediate mitigation should focus on restricting access to the ArcGIS Feature Service endpoints by implementing network-level controls such as firewalls, VPNs, or IP whitelisting to limit exposure to trusted users only.
  2. Monitor network traffic for unusual SQL command patterns or anomalous requests targeting ArcGIS services using intrusion detection/prevention systems (IDS/IPS).
  3. Employ Web Application Firewalls (WAF) with custom rules to detect and block SQL injection attempts specific to ArcGIS Feature Service operations.
  4. Regularly audit and review ArcGIS Server logs for suspicious activities indicative of exploitation attempts.
  5. Coordinate closely with Esri for timely release and deployment of official patches or security updates addressing this vulnerability.
  6. If patching is not immediately possible, consider disabling or limiting the vulnerable Feature Service operations temporarily.
  7. Implement least privilege principles on database accounts used by ArcGIS Server to minimize the impact of potential SQL injection exploitation.
  8. Conduct security awareness training for administrators and developers on secure coding and configuration practices related to geospatial services.
  9. Prepare an incident response plan specific to geospatial data compromise scenarios to enable rapid containment and recovery.

Description

A SQL Injection vulnerability exists in Esri ArcGIS Server versions 11.3, 11.4 and 11.5 on Windows, Linux and Kubernetes. This vulnerability allows a remote, unauthenticated attacker to execute arbitrary SQL commands via a specific ArcGIS Feature Service operation. Successful exploitation can potentially result in unauthorized access, modification, or deletion of data from the underlying Enterprise Geodatabase.

References

Community reviews

Loading reviews…