CVE-2021-29104
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 (XXS) vulnerability in ArcGIS Server Manager version 10.8.1 and below may allow a remote unauthenticated attacker to pass and store malicious strings in the ArcGIS Server Manager application.
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 confidenceA stored Cross Site Scripting (XSS) vulnerability in ArcGIS Server Manager version 10.8.1 and below allows a remote unauthenticated attacker to inject and persist malicious script content through user input fields, which then executes in the browsers of other users accessing the Manager interface.
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.0CVSS 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 if ArcGIS Server is deployedCheck running services or installed applications for Esri ArcGIS Server componentsAffected if ArcGIS Server is present in the environment
-
Determine the installed ArcGIS Server versionAccess the ArcGIS Server Administrator Directory or check the software version through the Manager interface or system utilitiesAffected if The installed version is 10.8.1 or below, or any version prior to 10.9.0
-
Verify Manager interface accessibilityCheck if the ArcGIS Server Manager web interface is accessible (typically at /manager/ URL path)Affected if The Manager interface is exposed and reachable
-
Confirm user input acceptance in ManagerLog into the Manager interface and identify input fields that accept user-supplied data (such as service names, descriptions, or configuration fields)Affected if User input fields exist and accept data without visible sanitization indicators
-
Check for existing malicious contentReview any saved configurations, service descriptions, or custom settings in the Manager for unexpected script tags or suspicious HTML contentAffected if Unexpected script tags, iframe elements, or javascript: URIs are found in stored Manager configurations
The environment is affected if ArcGIS Server version 10.8.1 or below is installed and the Manager interface is accessible and accepts user input.
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 data10.9.0
Apply the vendor-supplied patch for this vulnerability or upgrade to a patched version of ArcGIS Server; implement robust input validation and output encoding on all user-supplied data entering the application.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29104 — 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-2021-29104 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