CVE-2024-38039
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 an HTML injection vulnerability in Esri Portal for ArcGIS versions 11.0 and below that may allow a remote, authenticated attacker to create a crafted link which when clicked could render arbitrary HTML in the victim’s browser (no stateful change made or customer data rendered).
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 confidenceEsri Portal for ArcGIS versions 11.0 and below contains an HTML injection vulnerability where an authenticated remote attacker can craft malicious links that render arbitrary HTML in a victim's browser when clicked. Unlike XSS, this does not result in stateful changes or customer data exposure, but could be used for phishing or defacement.
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<= 11.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
- 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.
-
Identify the installed Portal for ArcGIS versionAccess the Portal Administrator Directory (typically at https://[hostname]/portal/admin/system/platforms/portal) or check the installation directory for version information, or query the portal's REST API endpoint for system infoAffected if The installed version is 11.0 or any version below 11.0 (e.g., 10.9.x, 10.8.x, etc.)
-
Verify the portal is accessible over the networkConfirm that the portal web interface is reachable via HTTP/HTTPS from network locations where attackers could potentially originate requestsAffected if The portal is externally accessible or accessible from untrusted network segments without additional controls
-
Confirm authentication is enabled for the portalCheck the portal security settings through the Administrator Directory to ensure user authentication is required for accessAffected if The portal allows unauthenticated access, as the CVE requires an authenticated attacker (though any authenticated user could be the attacker)
-
Review recent portal access logs for suspicious link patternsExamine portal audit logs or web server logs for unusual URL patterns that may contain HTML tags in parameters, particularly in areas where user content is rendered back to other usersAffected if Evidence exists of maliciously crafted links with HTML content being processed by the portal
The environment is affected if Esri Portal for ArcGIS is installed at version 11.0 or below and the portal is accessible to authenticated users who could craft and distribute malicious 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.
From vendor dataApply vendor-supplied patch when available; until then, implement URL filtering and warn users about clicking untrusted links within the portal. Consider restricting authentication to trusted users to reduce attack surface.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38039 — 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-2024-38039 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