dbcve.org
Field AnalyticsApplication · Sick

CVE-2025-49190

MEDIUM · 5.8 CVSS v3.1 Published 2025-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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
The application is vulnerable to Server-Side Request Forgery (SSRF). An endpoint can be used to send server internal requests to other ports.

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 confidence

The application is vulnerable to Server-Side Request Forgery (SSRF). An endpoint can be manipulated to make server-side requests to internal ports, potentially allowing attackers to access internal services, bypass network segmentation, or enumerate internal infrastructure.

MitigationImplement strict allowlist validation for any URL/hostname parameters, restrict the URL schemes and ports that can be accessed, and apply network segmentation to limit the server's ability to reach internal 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
Field AnalyticsApplication
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/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. Confirm Sick Field Analytics installation
    Locate and identify any Sick Field Analytics software running in your environment. Check installed applications, running services, or container images for this product.
    Affected if Sick Field Analytics is present in the environment
  2. Identify exposed web endpoints
    Review the application's exposed HTTP/HTTPS endpoints, typically through web server configuration files, reverse proxy settings, or API documentation.
    Affected if The application exposes web-facing endpoints that accept user-supplied URLs or hostnames as parameters
  3. Locate URL/hostname input parameters
    Examine application endpoints for parameters that accept URLs, hostnames, or IP addresses as input. Common parameter names include 'url', 'uri', 'endpoint', 'host', 'port', 'redirect', 'next', 'data', 'reference', 'site', 'html', 'val', 'validate', 'domain', 'callback', 'return', 'page', 'feed', 'host', 'port', 'path', 'ext', 'file', 'dir', 'query', 'base', 'class', 'do', 'function', 'op', 'g', 'sf', 'k', 'v', 'a', 'm', 's', 'd', 'c', 'n'. Use web proxy or grep through source/config files.
    Affected if Any endpoint accepts URL or hostname parameters without documented business justification
  4. Verify SSRF protections exist
    Inspect application code or configuration for validation of URL schemes (whitelist http/https only), hostname validation, port restrictions, or DNS resolution checks before making outbound requests.
    Affected if No URL validation, scheme restrictions, or port limitations are implemented on endpoint parameters that accept URLs/hostnames
  5. Review outbound request logs
    Examine application logs, proxy logs, or WAF logs for suspicious outbound requests to internal IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), localhost, or internal services from the application server.
    Affected if Evidence exists of requests to internal infrastructure originating from the application that were not initiated by legitimate business functions

You are affected if Sick Field Analytics is running and exposes any endpoint that accepts URL or hostname parameters without proper validation or restrictions.

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 allowlist validation for any URL/hostname parameters, restrict the URL schemes and ports that can be accessed, and apply network segmentation to limit the server's ability to reach internal resources.

Fix this in Field Analytics Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49190 — 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-49190 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