CVE-2019-16193
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 · uneditedIn ArcGIS Enterprise 10.6.1, a crafted IFRAME element can be used to trigger a Cross Frame Scripting (XFS) attack through the EDIT MY PROFILE feature.
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 confidenceCross Frame Scripting (XFS) vulnerability in ArcGIS Enterprise 10.6.1's Edit My Profile feature allows injection of malicious IFRAME elements, potentially enabling session hijacking or phishing attacks through frame-based content injection.
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.6.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify ArcGIS Enterprise versionAccess ArcGIS Portal Administrator Directory (typically at https://<server>/portal/admin) or check the 'About' page in ArcGIS Enterprise. Look for the version number in system info or product information.Affected if The installed version is exactly 10.6.1
-
Confirm Edit My Profile feature is accessibleLog into ArcGIS Portal as an authenticated user and navigate to My Profile or Profile settings (usually found at https://<server>/portal/home/user/profile.html or through the user menu). Verify the profile editing interface loads.Affected if The Edit My Profile feature is enabled and accessible to users
-
Check if application can be embedded in iframesExamine the HTTP response headers from the ArcGIS Portal web application using browser dev tools or a tool like curl. Look for X-Frame-Options or Content-Security-Policy headers.Affected if X-Frame-Options header is missing, or CSP does not include frame-ancestors restrictions, allowing the portal to be embedded in iframes on unauthorized domains
-
Test for iframe injection in profile fieldsIn the Edit My Profile interface, attempt to input an IFRAME tag (such as <iframe src="example.com"></iframe>) into profile fields like bio, title, or description. Save the profile and view it to see if the iframe renders.Affected if The iframe tag is rendered literally in the profile page, indicating the application fails to sanitize IFRAME injection attempts
A user is affected if they are running ArcGIS Enterprise exactly version 10.6.1, have the Edit My Profile feature accessible, and the application can be embedded in iframes without proper sanitization of IFRAME tags in profile fields.
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.
From vendor dataImplement proper input validation and sanitization on the Edit My Profile feature, and configure Content Security Policy (CSP) headers to prevent the application from being embedded in unauthorized iframes.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16193 — 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-2019-16193 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