dbcve.org
Field AnalyticsApplication · Sick

CVE-2025-49192

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 1.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 web application is vulnerable to clickjacking attacks. The site can be embedded into another frame, allowing an attacker to trick a user into clicking on something different from what the user perceives. This could potentially reveal confidential information or allow others to take control of their computer while clicking on seemingly innocuous objects.

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

The web application lacks proper framing protections (X-Frame-Options or Content-Security-Policy frame-anscestors headers), allowing it to be embedded in iframes on attacker-controlled pages. This enables clickjacking attacks where transparent or disguised overlay elements trick users into clicking unintended actions.

MitigationAdd X-Frame-Options: DENY or SAMEORIGIN header, or configure Content-Security-Policy with frame-anscestors directive to restrict framing to trusted origins.

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
Media ServerApplication
Affected:< 1.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Inspect HTTP response headers for X-Frame-Options
    Use a browser developer tool, curl -I, or a proxy to capture the HTTP response headers from the application's main page and any authenticated endpoints. Look for the presence of the X-Frame-Options header.
    Affected if The X-Frame-Options header is absent from the response, meaning the header is not set to DENY or SAMEORIGIN.
  2. Inspect HTTP response headers for Content-Security-Policy frame-ancestors
    Review the HTTP response headers for a Content-Security-Policy header. Check if it includes the frame-ancestors directive with allowed sources.
    Affected if The Content-Security-Policy header is absent or does not contain the frame-ancestors directive, allowing the site to be framed by any origin.
  3. Check Sick Media Server version
    Locate the Sick Media Server installation and determine its version number using the product's built-in about page, version info in the administrative interface, or product documentation for version identification methods.
    Affected if The installed version of Sick Media Server is lower than 1.5.
  4. Check Sick Field Analytics version
    Locate the Sick Field Analytics installation and determine its version number using the product's built-in about page, version info in the administrative interface, or product documentation for version identification methods.
    Affected if Any version of Sick Field Analytics is installed, as all versions are affected.

A user is affected if their Sick Field Analytics is any version, or their Sick Media Server is below version 1.5, AND the application does not send X-Frame-Options or Content-Security-Policy frame-ancestors headers in HTTP responses.

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.

dbcve · scoped
Upgrade available Upgrade to 1.5 or later
Fixed in 1.5
Interim mitigation

Add X-Frame-Options: DENY or SAMEORIGIN header, or configure Content-Security-Policy with frame-anscestors directive to restrict framing to trusted origins.

Recommended fix Moderate confidence

Media Server: version 1.5 or later; Field Analytics: contact vendor for patched release

  1. 1. For Media Server: Upgrade to version 1.5 or later to obtain the fixed release that addresses the clickjacking vulnerability.
  2. 2. For Field Analytics: Contact SICK vendor support to obtain a patched release or guidance, as all versions are affected.
  3. 3. Implement X-Frame-Options: DENY header on all web responses as an additional mitigation.
  4. 4. Alternatively, configure Content-Security-Policy: frame-ancestors 'none' to prevent framing.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Field Analytics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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