CVE-2022-38210
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 reflected HTML injection vulnerability in Esri Portal for ArcGIS versions 10.9.1 and below that may allow a remote, unauthenticated attacker to create a crafted link which when clicked could render arbitrary HTML 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 confidenceReflected HTML injection (XSS) vulnerability in Esri Portal for ArcGIS versions 10.9.1 and below allows remote, unauthenticated attackers to craft malicious links that render arbitrary HTML in victim browsers via reflected input.
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.9.1CVSS 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.
-
Check Portal for ArcGIS versionLog into Portal for ArcGIS as an administrator, navigate to Organization > Settings > About, or use the ArcGIS Portal Administrator Directory at https://<hostname>:7080/arcgis/portal/admin to view the version information.Affected if The displayed version is 10.9.1 or any version lower than 10.9.1 (e.g., 10.9, 10.8.1, 10.8, etc.)
-
Verify web-tier services are accessibleConfirm that the Portal for ArcGIS web interface is reachable over HTTP/HTTPS. Try accessing the portal URL directly in a browser.Affected if The portal web application responds to requests, making it possible for attackers to craft malicious links targeting portal users.
-
Identify exposed parameters in portal URLsReview common portal endpoints such as the home page, search results, and item detail pages. Observe URL parameters that reflect user input back into the HTML response without encoding.Affected if Any parameter in the URL (such as q, search, or id) reflects unsanitized input directly into the page content.
You are affected if Esri Portal for ArcGIS is running version 10.9.1 or below and the web interface is accessible to unauthenticated users, allowing attackers to inject malicious HTML via crafted links.
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.
dbcve · scopedApply Esri's official patch for this vulnerability or upgrade to a patched version; implement output encoding and input validation on affected parameters as compensating controls if no patch is available.
Portal for ArcGIS version > 10.9.1 (e.g., 10.9.2 or later stable release)
- Check the current Portal for ArcGIS version by navigating to the organization settings or using the ArcGIS Portal Admin Directory
- Review Esri's official security advisories at www.esri.com to identify the specific fixed release for this vulnerability
- Plan and schedule an upgrade to a Portal for ArcGIS version higher than 10.9.1 (such as 10.9.2 or the next available stable release)
- Before upgrading, review Esri's upgrade documentation and perform a backup of the portal configuration
- Execute the upgrade following Esri's standard upgrade procedures for Portal for ArcGIS
- After upgrade, verify the organization is functional and test that the vulnerability is no longer reproducible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38210 — 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-2022-38210 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