dbcve.org
Portal For ArcgisApplication · Esri

CVE-2024-25691

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 XSS vulnerability in Esri Portal for ArcGIS versions 11.1 and below which may allow 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

Reflected XSS vulnerability in Esri Portal for ArcGIS versions 11.1 and below allows a remote, unauthenticated attacker to embed malicious JavaScript into a crafted URL. When a victim clicks the link, the unvalidated input is reflected back and executed in their browser, enabling session hijacking, credential theft, or phishing attacks.

MitigationUpgrade Esri Portal for ArcGIS to version 11.2 or later, which contains the security fix. Alternatively, apply the vendor-supplied patch if available and implement URL parameter validation/sanitization on affected endpoints as a temporary measure.

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:= 10.8.1= 10.9.1= 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 Esri Portal for ArcGIS installation
    Check for Portal for ArcGIS by accessing the web portal login page at /portal/home or /arcgis/home, or check for the installation directory on the server
    Affected if The product is Esri Portal for ArcGIS
  2. Determine installed version
    Access the Portal Administrator Directory at /portal/admin/info and locate the 'currentVersion' field, or check the About page in the portal interface
    Affected if The version is 10.8.1, 10.9.1, or 11.1 exactly
  3. Confirm web access is enabled
    Verify the portal web adapter is accessible and responding on the network by accessing the portal URL
    Affected if The web interface is accessible to users who could click malicious links

A user is affected if they are running Esri Portal for ArcGIS version 10.8.1, 10.9.1, or 11.1 with the web portal interface accessible to end users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Esri Portal for ArcGIS to version 11.2 or later, which contains the security fix. Alternatively, apply the vendor-supplied patch if available and implement URL parameter validation/sanitization on affected endpoints as a temporary measure.

Recommended fix Moderate confidence

Portal for ArcGIS 11.2 or later (verify latest version via Esri Customer Portal)

  1. 1. Identify the current Portal for ArcGIS version by navigating to the portal admin directory (e.g., https://portal.domain.com/portal/portaladmin) and checking the system info.
  2. 2. Plan for upgrade during a maintenance window as the upgrade will require downtime.
  3. 3. Backup the portal configuration and content database before proceeding with the upgrade.
  4. 4. Download the latest Portal for ArcGIS installer from the Esri Customer Portal (requires active maintenance).
  5. 5. Run the installer on the portal machine, following the upgrade installation guide in Esri documentation.
  6. 6. Verify the upgrade was successful by logging into the portal and confirming the version in the about page.
  7. 7. Test critical workflows to ensure the portal is functioning correctly post-upgrade.
Caveat Upgrading to a new minor version (e.g., 11.1 to 11.2) may require changes to custom configurations or integrations; review Esri's upgrade guide and breaking changes documentation

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

Fix this in Portal For Arcgis Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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