CVE-2024-25709
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 · uneditedThere is a stored Cross‑Site Scripting (XSS) vulnerability in Esri Portal for ArcGIS versions 11.2 and below that may allow a remote, authenticated attacker to create a crafted link that can be saved as a new location when moving an existing item, which could potentially execute arbitrary JavaScript code in a victim’s browser. Exploitation does not require any privileges and can be performed by an anonymous user.
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 confidenceA stored Cross-Site Scripting vulnerability in Esri Portal for ArcGIS allows an authenticated attacker to embed malicious JavaScript within a crafted link that gets saved as a new location when moving an existing item, potentially executing arbitrary code in victim browsers.
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= 10.8.1= 10.9.1= 11.0= 11.1= 11.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Esri Portal for ArcGIS installationCheck if the system runs Esri Portal for ArcGIS by accessing the Portal Administrator Directory at https://<host>/arcgis/portal/admin or checking for ArcGIS Portal web application files.Affected if The product is not Esri Portal for ArcGIS.
-
Determine installed Portal versionNavigate to the Portal Administrator Directory and click 'System' > 'Properties' > 'View JSON' to find the 'portalVersion' value, or check the installed version through the ArcGIS Portal landing page footer.Affected if The installed version is 10.8.1, 10.9.1, 11.0, 11.1, or 11.2.
-
Verify authenticated user access to item managementConfirm that authenticated portal users can access the content API or UI to move items. Check if users with standard (non-admin) roles can create and move items between folders.Affected if Standard authenticated users have permission to move items.
-
Inspect item locations for stored scriptsUse the Portal Content API (POST /arcgis/sharing/rest/content/items/<itemID>/move) or browse the content directory to examine the 'url' or location fields of existing items for unsanitized HTML or JavaScript code patterns.Affected if Any item contains suspicious script tags, javascript: URIs, or event handlers in location/URL fields.
-
Review item move operation logsAccess Portal logs via the Administrator Directory under 'Logs' > 'Query' and search for 'move' operations that occurred around the time of potential exploitation. Look for entries with unusual URL or location parameters.Affected if Move operations contain encoded or raw script payloads in location parameters.
A user is affected if they run Esri Portal for ArcGIS versions 10.8.1 through 11.2 and authenticated users can access the item move functionality without sanitization of location fields.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a patched version of Esri Portal for ArcGIS or apply vendor-supplied security patches; validate and sanitize all user-supplied input when creating or moving items.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25709 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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