CVE-2025-49191
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 · uneditedLinked URLs during the creation of iFrame widgets and dashboards are vulnerable to code execution. The URLs get embedded as iFrame widgets, making it possible to attack other users that access the dashboard by including malicious code. The attack is only possible if the attacker is authorized to create new dashboards or iFrame widgets.
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 confidenceAuthenticated users with dashboard/widget creation privileges can embed malicious URLs as iFrame widgets. When other users view these dashboards, the embedded iFrame content can execute arbitrary JavaScript in their browser context, leading to session hijacking or further code execution. This is a stored XSS vulnerability leveraging iFrame source injection.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Sick Field Analytics installationIdentify if Sick Field Analytics software is deployed in your environment by checking installed applications, running services, or documentation. There is no specific version range since all versions are affected.Affected if The software is present and running in your environment.
-
Verify dashboard/widget creation privilegesReview user role configurations and access control settings to determine which authenticated users have permission to create or edit dashboards and widgets. Check for roles with dashboard/widget creation capabilities.Affected if Any authenticated user role grants dashboard or widget creation privileges.
-
Inspect existing iFrame widgets for external sourcesAccess the dashboard editor or configuration panel as a user with creation privileges. Navigate to widget settings and examine any iFrame widgets present. Inspect the src attribute of each iFrame widget to identify the URL source.Affected if iFrame widgets exist with src attributes pointing to untrusted or external domains that are not on an allowlist.
-
Check for unsanitized user-created dashboard contentExport or review stored dashboard configuration files or database entries containing widget definitions. Look for iFrame src values that contain JavaScript protocols, data URIs, or domains outside your trusted network.Affected if Stored dashboard data contains iFrame src values with javascript: URLs, data: URIs, or unvalidated external domains.
You are affected if Sick Field Analytics is deployed and users with dashboard creation privileges can embed arbitrary URLs into iFrame widgets, allowing stored XSS when other users view those dashboards.
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.
From vendor dataImplement strict allowlist-based URL validation for iFrame widget sources, apply Content Security Policy (CSP) frame-ancestors directive, and sanitize or restrict iFrame src attributes to trusted domains only.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49191 — 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-49191 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