dbcve.org
Portal For ArcgisApplication · Esri

CVE-2024-25695

HIGH · 7.2 CVSS v3.1 Published 2024-04-04
Fix available
A fix is available. Upgrade to after 11.2 or later.
See remediation →
81/100
Remediation priority · High
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
There is a Cross-site Scripting vulnerability in Portal for ArcGIS in versions 11.2 and below that may allow a remote, authenticated attacker to provide input that is not sanitized properly and is rendered in error messages. The are no privileges required to execute this attack.

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 · moderate confidence

Cross-site Scripting (XSS) vulnerability in Portal for ArcGIS versions 11.2 and below where authenticated attackers can inject unsanitized input that gets rendered in error messages, allowing execution of malicious scripts in user browsers.

MitigationApply the vendor patch for Portal for ArcGIS 11.2 or later; implement input validation and output encoding for all user-supplied data displayed in error messages.

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.2

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Determine Portal for ArcGIS installed version
    Access the ArcGIS Portal Administrator Directory (typically at https://<hostname>/portal/admin) and navigate to System > Properties > Update Properties, or check the About page in the Portal website. Alternatively, check the installation logs or use the 'arcgisportaladmin' utility if available locally.
    Affected if The installed version is 11.2 or any version below 11.2 (e.g., 11.1, 11.0, 10.9.x, etc.)
  2. Verify Portal is accessible over the network
    Confirm the Portal for ArcGIS web interface is reachable at its configured URL (e.g., https://<server>/portal). Check that the portal homepage loads and accepts authentication.
    Affected if The Portal is publicly or internally accessible and accepts user logins, providing an attack surface for authenticated XSS injection.
  3. Identify active user authentication methods
    In the Portal Administrator Directory, navigate to Security > Configuration > Update Authentication and review enabled authentication providers (e.g., built-in ArcGIS, Enterprise identity store, SAML, OAuth).
    Affected if One or more authentication methods are enabled, allowing attackers to obtain valid sessions for injecting malicious scripts into error messages.
  4. Review error message handling in custom configurations
    Examine any custom configurations, apps, or templates that integrate with Portal and display error messages to users. Check the Portal logs (typically in <install_dir>/arcgis/portal/usr/logs) for any custom error handlers or HTML-rendered messages.
    Affected if Custom applications or configurations render user-supplied input in error messages without sanitization, enabling XSS.

A user is affected if Portal for ArcGIS is version 11.2 or below, is network-accessible, and accepts authenticated sessions that could trigger unsanitized error messages.

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

Apply the vendor patch for Portal for ArcGIS 11.2 or later; implement input validation and output encoding for all user-supplied data displayed in error messages.

Recommended fix Moderate confidence

Portal for ArcGIS 11.3 or later (verify with Esri's official release notes)

  1. 1. Check Esri's official support site (support.esri.com) for the latest available version of Portal for ArcGIS
  2. 2. Download and review the release notes for the newer version to confirm it includes the fix for CVE-2024-25695
  3. 3. Plan an upgrade window and back up the current Portal for ArcGIS configuration
  4. 4. Upgrade Portal for ArcGIS to the version that includes the security fix (typically the next major or minor release after 11.2)
  5. 5. After upgrade, verify the error message rendering behavior has been patched and test for XSS vulnerabilities
Caveat Review Esri's upgrade documentation for any configuration or compatibility changes between 11.2 and the target version

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

Fix this in Portal For Arcgis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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