CVE-2024-25692
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.1 and below that may in some cases allow a remote, unauthenticated attacker to trick an authorized user into executing unwanted actions via a crafted form. The impact to Confidentiality and Integrity vectors is limited and of low severity.
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 confidenceCSRF vulnerability in Esri Portal for ArcGIS 11.1 and below allows remote, unauthenticated attackers to trick authenticated users into submitting crafted forms that execute unwanted actions on the portal. The attacker leverages the trusted session of an authenticated user without their consent.
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.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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 or check the About page in the portal interface to retrieve the exact version numberAffected if The installed version is 11.1 or lower (any version up to and including 11.1)
-
Verify the portal is accessible over networkConfirm the Esri Portal for ArcGIS web interface is reachable and accepts user authenticationAffected if The portal is running and accessible to users on the network
-
Confirm user authentication is enabledCheck that the portal has user authentication enabled and users can log in to their accountsAffected if Users are authenticated to the portal and have active sessions
-
Assess CSRF protection statusReview the portal configuration or HTTP responses for presence of anti-CSRF tokens in forms and SameSite cookie attributes - examine form submission requests from the portalAffected if Forms submitted to the portal lack anti-CSRF token validation and cookies lack SameSite attributes, allowing cross-origin form submissions to execute
A user is affected if their Esri Portal for ArcGIS installation is version 11.1 or below and the portal lacks proper anti-CSRF token validation on forms, enabling attackers to trigger unauthorized actions through the trusted session of an authenticated user.
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 vendor patch when released; in interim, implement anti-CSRF tokens and SameSite cookie attributes as defense-in-depth while users avoid clicking untrusted links.
Portal for ArcGIS 11.2 or later
- Verify the current Portal for ArcGIS version by accessing the Portal Administrator Directory and checking the version information
- Obtain and download the latest Portal for ArcGIS version 11.2 or later from the Esri Customer Portal or official distribution channels
- Review the Esri Portal for ArcGIS upgrade documentation and pre-upgrade checklist
- Ensure proper backups of the Portal for ArcGIS configuration, content, and user directories are completed
- Schedule a maintenance window appropriate for the upgrade operation
- Execute the Portal for ArcGIS upgrade following the official Esri upgrade procedure
- After upgrade completes, verify the Portal for ArcGIS services are running correctly
- Validate that the CSRF protection is functioning by testing the vulnerability scenario or reviewing the security configuration
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-25692 — 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-25692 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