dbcve.org
Portal For ArcgisApplication · Esri

CVE-2024-25698

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-04
Fix available
A fix is available. Upgrade to after 11.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
There is a reflected cross site scripting vulnerability in the home application in Esri Portal for ArcGIS 11.1 and below on Windows and Linux that allows a remote, unauthenticated attacker to create a crafted link which when clicked could potentially execute arbitrary JavaScript code in the victim’s browser.

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 reflected cross-site scripting (XSS) vulnerability exists in the home application of Esri Portal for ArcGIS 11.1 and below on Windows and Linux. Remote, unauthenticated attackers can craft malicious links that, when clicked by victims, execute arbitrary JavaScript code in their browsers.

MitigationApply the vendor patch or upgrade to ArcGIS Portal 11.2 or later; implement input validation and output encoding in the home application to prevent XSS injection.

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
Portal For ArcgisApplication
Affected:<= 11.1

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
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 checks

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

  1. Identify the installed Esri Portal for ArcGIS version
    Access the ArcGIS Portal Administrator Directory or check system documentation to determine the exact version number of the installed Portal instance
    Affected if The installed version is 11.1 or lower
  2. Confirm the home application is accessible
    Navigate to the /home/ endpoint of the Portal and verify the application loads successfully
    Affected if The home application is reachable and functional without authentication
  3. Test for reflected parameters in the home application
    Submit a test request to the home application with a harmless marker in the URL parameters (such as a test value in redirect, url, or returnUrl parameters) and examine if the response reflects this value back without HTML encoding
    Affected if The home application reflects user-supplied parameter values in its response without proper output encoding

If the installed Portal for ArcGIS version is 11.1 or below AND the home application is accessible AND URL parameters are reflected unencoded in responses, the environment is vulnerable to CVE-2024-25698.

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.1
Interim mitigation

Apply the vendor patch or upgrade to ArcGIS Portal 11.2 or later; implement input validation and output encoding in the home application to prevent XSS injection.

Recommended fix Moderate confidence

Portal for ArcGIS 11.2 or later

  1. 1. Verify the current Portal for ArcGIS version by navigating to the ArcGIS Portal Administrator Directory and checking the version information.
  2. 2. Back up the Portal for ArcGIS configuration and data according to Esri backup procedures.
  3. 3. Download the latest version of Portal for ArcGIS from the Esri Customer Portal or download the appropriate patch if provided by Esri.
  4. 4. Follow the Esri upgrade guide for Portal for ArcGIS to install the newer version.
  5. 5. After upgrade, verify the XSS vulnerability is remediated by testing that the crafted link no longer executes arbitrary JavaScript.
Caveat Review Esri's upgrade documentation for any configuration changes or migration requirements between versions

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

Fix this in Portal For Arcgis Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25698 — 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-2024-25698 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