CVE-2025-49189
Sick Media Server ≤ 1.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2025-49189 is a medium-severity Sensitive Cookie Without 'HttpOnly' Flag (CWE-1004) vulnerability in Sick Media Server. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steal Web Session Cookie (T1539); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18180
Vulnerability Data
The HttpOnlyflag of the session cookie \"@@\" is set to false. Since this flag helps preventing access to cookies via client-side scripts, setting the flag to false can lead to a higher possibility of Cross-Side-Scripting attacks which target the stored…
more
cookies.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Proper implementation of session authenticity requires marking sensitive session cookies HttpOnly so that client scripts cannot access them.
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.
Broad SDLC practices catch cookie-handling defects via standards/testing (mostly forward) yet remain too general to guarantee this narrow flag setting is always enforced (partial reverse).
Role-based training can reduce the chance developers introduce missing HttpOnly flags but supplies no enforcement or detection, leaving essentially all of the implementation flaw's risk intact.
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 HttpOnly flags but does not prevent the weakness.
Application security requirements can mandate HttpOnly on sensitive cookies.
Secure coding standards explicitly require the HttpOnly flag for sensitive cookies.