Portal For ArcgisApplication · Esri

CVE-2022-38186

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-15
Fix available
A fix is available. Upgrade to after 10.8.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 XSS vulnerability in Esri Portal for ArcGIS versions 10.8.1 and below which may allow a remote attacker able to convince a user to click on a crafted link which 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 · moderate confidence

A reflected XSS vulnerability exists in Esri Portal for ArcGIS versions 10.8.1 and below. An attacker can craft a malicious URL containing JavaScript payload that executes in the victim's browser when clicked, due to improper input validation and output encoding on the affected endpoint.

MitigationApply vendor-supplied patch/upgrade to a fixed version (10.9+) and implement output encoding and input validation on the affected parameter to prevent script execution.

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

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. Confirm Esri Portal for ArcGIS installation
    Identify whether Portal for ArcGIS is installed on the system by checking for the Portal service or installation directory
    Affected if Portal for ArcGIS software is present on the system
  2. Check installed Portal version
    Access the Portal Administrator Directory (typically at /portal/portaladmin) or check system information to retrieve the exact version number
    Affected if Installed version is 10.8.1 or below (any version from 10.0 through 10.8.1)
  3. Identify the vulnerable endpoint
    Locate the web endpoint affected by improper input validation and output encoding - this is the specific URL parameter that accepts user input without sanitization
    Affected if The endpoint with the input validation flaw is accessible and accepts unsanitized parameters
  4. Verify the parameter is exploitable
    Inspect whether the affected parameter in the URL reflects user-supplied input back into the response without proper encoding
    Affected if The endpoint reflects unsanitized input in its response, enabling script injection

If Portal for ArcGIS is installed and the version is 10.8.1 or below, and the vulnerable endpoint with improper input validation is accessible, the environment is affected by this reflected XSS vulnerability.

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 10.8.1
Interim mitigation

Apply vendor-supplied patch/upgrade to a fixed version (10.9+) and implement output encoding and input validation on the affected parameter to prevent script execution.

Recommended fix Moderate confidence

Portal for ArcGIS 10.9 or later

  1. Identify the current Portal for ArcGIS version in use (check the About page in Portal Admin)
  2. Review the Esri Product Lifecycle and patches page at https://www.esri.com/en-us/portal/overview for the fixed release
  3. Upgrade Portal for ArcGIS to version 10.9 or later (the first release after 10.8.1 that addresses this vulnerability)
  4. After upgrade, verify the XSS vulnerability is patched by testing with the originally vulnerable parameter
  5. Confirm normal Portal functionality works after the upgrade
Caveat Standard upgrade considerations apply - review Esri upgrade documentation, backup your portal content and config, test in non-production first

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-2022-38186 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38186 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