CVE-2023-25832
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 cross-site-request forgery vulnerability in Esri Portal for ArcGIS Versions 11.0 and below that may allow an attacker to trick an authorized user into executing unwanted actions.
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 confidenceA cross-site-request forgery (CSRF) vulnerability exists in Esri Portal for ArcGIS versions 11.0 and below. The flaw allows remote attackers to trick authenticated users into unknowingly executing unauthorized actions by exploiting the lack of proper anti-CSRF tokens or referer validation in the application's web 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<= 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Esri Portal for ArcGIS versionAccess the ArcGIS Portal Administrator Directory or portal home page and locate the version information, typically found in the system information or about sectionAffected if The installed version is 11.0 or below
-
Inspect web interface for anti-CSRF tokensExamine the HTML source or network responses of the portal's web interface, specifically forms and AJAX requests that perform state-changing operations, to determine if unique anti-CSRF tokens are includedAffected if State-changing forms or requests do not contain anti-CSRF token parameters
-
Verify referer header validationReview the web server or application configuration to check if the portal validates the referer header for state-changing requests, or test by submitting requests with missing or altered referer headersAffected if Referer validation is not enforced or can be bypassed for state-changing operations
-
Confirm authentication mechanismDetermine if the portal uses token-based or session-based authentication for user logins, as the CSRF flaw affects authenticated user sessionsAffected if Users can authenticate to the portal and session cookies are used without SameSite attributes
A user is affected if their Esri Portal for ArcGIS installation is version 11.0 or below and the web interface lacks anti-CSRF tokens or proper referer validation for state-changing operations.
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 the vendor-provided security patch for Esri Portal for ArcGIS 11.0 (or upgrade to a patched version). Additionally, implement SameSite cookie attributes and server-side CSRF token validation for all state-changing operations as a defense-in-depth measure.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25832 — 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-2023-25832 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