dbcve.org
Arcgis ServerApplication · Esri

CVE-2025-57870

CRITICAL · 10.0 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to after 11.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A critical SQL injection vulnerability in Esri ArcGIS Server versions 11.3-11.5 allows remote unauthenticated attackers to execute arbitrary SQL commands through a specific ArcGIS Feature Service operation, potentially compromising the underlying Enterprise Geodatabase.

MitigationApply vendor-supplied patches or upgrade to a non-vulnerable version. If immediate patching is not possible, consider network segmentation to restrict access to ArcGIS services and deploy WAF rules to detect/block SQL injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Arcgis ServerApplication
Affected:>= 11.3, <= 11.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ArcGIS Server version
    Access ArcGIS Server Administrator Directory (typically at /arcgis/admin) or check the ArcGIS Server Manager About page to retrieve the exact version number
    Affected if The installed version is 11.3, 11.4, or 11.5
  2. Confirm Enterprise Geodatabase is configured
    Check ArcGIS Server manager or the data sources configuration to determine if an Enterprise Geodatabase (e.g., SQL Server, Oracle, PostgreSQL) is connected as a data store
    Affected if Enterprise Geodatabase is enabled and connected to the ArcGIS Server
  3. Verify ArcGIS Feature Service is exposed
    List published services through ArcGIS Server REST endpoint (typically /arcgis/rest/services) or Administrator API to identify if Feature Services are publicly accessible
    Affected if Feature Service endpoints are reachable from untrusted networks without authentication
  4. Review server logs for suspicious SQL patterns
    Access ArcGIS Server logs through Administrator Directory or Server Manager and search for anomalous SQL syntax, unexpected WHERE clauses, or UNION statements in Feature Service requests
    Affected if Logs contain SQL injection signatures or unexpected database query patterns
  5. Check network accessibility of ArcGIS services
    Verify whether ArcGIS Server endpoints (ports 6080/6443) are accessible from external/untrusted networks using network scanning tools or firewall rules review
    Affected if ArcGIS Server is directly exposed to the internet or untrusted networks

A user is affected if their ArcGIS Server runs version 11.3, 11.4, or 11.5 with an exposed Feature Service connecting to an Enterprise Geodatabase.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 11.5
Interim mitigation

Apply vendor-supplied patches or upgrade to a non-vulnerable version. If immediate patching is not possible, consider network segmentation to restrict access to ArcGIS services and deploy WAF rules to detect/block SQL injection attempts.

Recommended fix Moderate confidence

ArcGIS Server 11.6 or later (upgrade beyond the affected 11.3-11.5 range)

  1. 1. Back up your current ArcGIS Server configuration and data before proceeding with any upgrade.
  2. 2. Review Esri's official upgrade documentation for ArcGIS Server at www.esri.com for version 11.6 or later.
  3. 3. Download and install ArcGIS Server version 11.6 or the latest available version from Esri's support website.
  4. 4. Test the upgrade in a non-production environment to verify compatibility with your existing applications and workflows.
  5. 5. Deploy the upgraded ArcGIS Server to production after successful testing.
  6. 6. Verify that the SQL injection vulnerability is remediated by confirming the patch is applied.
Caveat Review Esri's release notes for version 11.6 for any breaking changes or deprecations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Arcgis Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57870 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data