# CVE-2025-1726: [#BUG-000172669 ArcGIS Monitor has a security vulnerability]

> Remote authenticated attackers can read limited encrypted database schema information via SQL injection in ArcGIS Monitor.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2025
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-pv4j-mj6q-vxrm

## What is CVE-2025-1726?

CVE-2025-1726 is a medium-severity SQL injection vulnerability in Esri ArcGIS Monitor, published on 26 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

There is a SQL injection issue in Esri ArcGIS Monitor versions 2023.0 through 2024.x on Windows and Linux that allows a remote, authenticated attacker with low privileges to improperly read limited database schema information by passing crafted queries. While it is possible to enumerate some internal database identifiers, the impact to the confidentiality vector is "LOW' because any sensitive data returned in a response is encrypted. There is no evidence of impact to the integrity or availability vectors. This issue is addressed in ArcGIS Monitor 2024.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-1726?


## How do I fix CVE-2025-1726?

No fix has been published for CVE-2025-1726 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-1726 being exploited?

There is no known exploitation of CVE-2025-1726 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1726 and fix it if it is affected.

What it is: CVE-2025-1726 is a medium-severity SQL injection vulnerability in Esri ArcGIS Monitor, published on 26 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1726 in the wild and no public exploit code.

Affected product: Esri ArcGIS Monitor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1726/ (Markdown: https://insights.sbomify.com/CVE-2025-1726/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1726
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1726
- OSV: https://osv.dev/vulnerability/CVE-2025-1726

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1726/
Summaries are generated and may contain mistakes; the official description above is the record.