CVE-2025-4967
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 · uneditedEsri Portal for ArcGIS 11.4 and prior allows a remote, unauthenticated attacker to bypass the Portal’s SSRF protections.
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 confidenceEsri Portal for ArcGIS 11.4 and prior contains a vulnerability that allows remote, unauthenticated attackers to bypass the product's built-in Server-Side Request Forgery (SSRF) protections, potentially enabling the server to be coerced into making arbitrary network requests to internal or external resources.
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.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 system documentation for the installed version (typically found in Portal Administrator > Organization > Settings > About, or via the /portal/portalinfo endpoint)Affected if The installed version is 11.4 or any version prior to 11.4
-
Confirm SSRF protection is configuredReview the Portal's security settings for Server-Side Request Forgery protection features (check under Portal Administrator > Security > Settings or similar security configuration areas)Affected if SSRF protection is enabled and configured, as the bypass specifically targets these protections
-
Inspect network configurationReview inbound and outbound network access rules for the Portal server (check firewall rules, network security groups, or proxy configuration)Affected if The Portal has unrestricted outbound network access allowing arbitrary HTTP requests
-
Review request logs for suspicious patternsExamine Portal access logs and network traffic logs for unusual outbound requests, especially to internal resources or unexpected external domains from the Portal serverAffected if Outbound requests from the Portal match patterns indicative of SSRF exploitation (requests to internal IPs, cloud metadata endpoints, or unexpected internal services)
The environment is affected if Esri Portal for ArcGIS version 11.4 or prior is running with SSRF protection enabled and the server has outbound network access, as attackers can bypass those protections to make arbitrary requests.
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 · scopedUpgrade to Esri Portal for ArcGIS version 11.5 or later which contains the fix for this SSRF protection bypass vulnerability.
Portal for ArcGIS 11.5 or later (or latest available stable release)
- 1. Check Esri Support Resources (support.esri.com or patches.esri.com) for the latest available patch or hotfix for CVE-2025-4967
- 2. If a hotfix is available, download it following Esri's standard patch deployment process
- 3. If no hotfix is available, plan an upgrade to the next stable release after 11.4 (e.g., 11.5 or later)
- 4. Before deploying in production, test the patch/upgrade in a staging environment
- 5. Apply the patch or complete the upgrade during a scheduled maintenance window
- 6. Verify the SSRF protection bypass is no longer exploitable after applying the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4967 — 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-2025-4967 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