dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-28963

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Server-Side Request Forgery (SSRF) vulnerability in Md Yeasin Ul Haider URL Shortener exact-links allows Server Side Request Forgery.This issue affects URL Shortener: from n/a through <= 3.0.7.

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 confidence

Server-Side Request Forgery (SSRF) vulnerability in the URL Shortener exact-links application allows attackers to craft malicious URLs that cause the server to make requests to internal resources, internal services, or unintended external destinations. This can enable reconnaissance of internal network infrastructure, access to cloud metadata services, and bypass of network segmentation controls.

MitigationImplement strict URL validation using an allowlist of permitted domains/IPs, disable dangerous URL schemes (file://, gopher://, ftp://), and enforce network segmentation to prevent the application server from accessing internal resources. Validate that URLs resolve to publicly accessible addresses before making outbound requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify exact-links installation
    Locate the exact-links application files or running service in your environment - check for application directories, containers, or deployed web apps named 'exact-links' or similar URL shortener implementations
    Affected if The exact-links URL Shortener application is present in your environment
  2. Confirm URL shortening feature is enabled
    Check if the application's URL shortening or redirect endpoint is accessible and actively processing requests - look for endpoints that accept URLs as input and return shortened links or perform redirects
    Affected if The URL shortening/redirect functionality is enabled and accepting user-supplied URLs
  3. Inspect URL validation logic
    Review the application's source code or configuration for URL validation routines - specifically look for allowlists, blocklists, or sanitization logic applied to user-provided URLs before making outbound requests
    Affected if No URL validation or allowlist-based domain filtering is implemented in the code handling URL shortening requests
  4. Check for dangerous URL scheme restrictions
    Examine the application's configuration or code to determine if URL schemes like file://, gopher://, ftp://, or internal IP addresses are explicitly blocked or restricted
    Affected if The application does not block dangerous URL schemes (file://, gopher://, ftp://) or internal IP addresses
  5. Verify network segmentation controls
    Check if the server running exact-links has outbound network restrictions configured - verify whether the application server can make arbitrary outbound HTTP/HTTPS requests to internal or external destinations
    Affected if The application server can initiate outbound connections to arbitrary internal or external URLs without network segmentation controls in place

You are affected if the exact-links URL Shortener application is deployed with its URL shortening feature enabled and lacks proper URL validation, scheme restrictions, and network segmentation controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation using an allowlist of permitted domains/IPs, disable dangerous URL schemes (file://, gopher://, ftp://), and enforce network segmentation to prevent the application server from accessing internal resources. Validate that URLs resolve to publicly accessible addresses before making outbound requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-28963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-28963 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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