CVE-2022-38190
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 · uneditedA stored Cross Site Scripting (XSS) vulnerability in Esri Portal for ArcGIS configurable apps may allow a remote, unauthenticated attacker to pass and store malicious strings via crafted queries which when accessed could potentially execute arbitrary JavaScript code in the user’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 confidenceThis is a stored Cross Site Scripting (XSS) vulnerability in Esri Portal for ArcGIS configurable apps where an unauthenticated remote attacker can inject malicious JavaScript code via crafted query parameters. The malicious payload is stored by the application and executes in the browser of any user who accesses the affected query.
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.8.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.
-
Identify installed Portal for ArcGIS versionAccess the ArcGIS Portal Administrator Directory and navigate to System > Properties > Update Properties, or check the About page in the Portal web interface. The version number is displayed there.Affected if The installed version is 10.8.1 or earlier (any version <= 10.8.1).
-
Confirm configurable apps are in useAccess the Portal for ArcGIS website and browse to the apps section (typically at /apps/ or /home/webmap/). Look for any configurable app templates such as CrowdSource Blog, CrowdSource Reporter, or similar story map applications.Affected if Any configurable app templates are published and accessible on the Portal.
-
Check for query parameter usage in app URLsReview the URLs of configured apps in the Portal. Look for apps that accept query parameters in the URL (examples: ?id=, ?title=, ?webmap=). Use browser developer tools or server access logs to capture full URLs.Affected if Configurable apps accept and process query parameters that could store malicious input.
-
Review web application logs for suspicious query patternsExamine Portal for ArcGIS HTTP access logs (typically found in the logs directory) for unusual query parameter patterns containing JavaScript tags (<script>, javascript:, onerror=, etc.) or URL-encoded equivalents.Affected if Logs contain requests with suspicious patterns in query parameters that may indicate exploitation attempts.
You are affected if your Portal for ArcGIS version is 10.8.1 or earlier AND you have configurable apps accessible that process query parameters, as the vulnerability allows stored XSS injection through those parameters.
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 the vendor patch or update to Esri Portal for ArcGIS to remediate the XSS vulnerability. If a patch is unavailable, consider disabling or removing the affected configurable app until remediation is possible.
10.9 or latest available Portal for ArcGIS release (check Esri Security Advisories for specific patch version)
- Check Esri Support site for the specific security patch for CVE-2022-38190
- Review the Esri Security Advisory for Portal for ArcGIS for detailed remediation steps
- Apply the latest available security patch for your current version, or plan upgrade to fixed release
- After patching/upgrade, verify the XSS vulnerability is resolved by testing configurable apps with crafted query parameters
- Monitor Esri product security bulletins for future security updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38190 — 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-38190 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