CVE-2025-49192
Sick Field Analytics
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NSummary
CVE-2025-49192 is a medium-severity Improper Restriction of Rendered UI Layers or Frames (CWE-1021) vulnerability in Sick Field Analytics. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18191
Vulnerability Data
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…
more
allow others to take control of their computer while clicking on seemingly innocuous objects.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require implementing frame-ancestors / X-Frame-Options controls that prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing frame protections, but does not itself implement the control.
Web filtering can block or sandbox untrusted frames, but does not enforce application-level frame-busting or CSP.
Application security requirements can mandate frame-ancestors / X-Frame-Options, directly addressing UI redressing risks.
Secure architecture principles include isolation of UI layers and proper use of browser security controls.
Secure coding practices directly require implementation of frame-busting headers or CSP frame-ancestors directives.