dbcve.org
In.sight B120\\37Hardware / appliance · Philips

CVE-2015-2883

MEDIUM · 5.4 CVSS v3.0 Published 2017-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Philips In.Sight B120/37 has XSS, related to the Weaved cloud web service, as demonstrated by the name parameter to deviceSettings.php or shareDevice.php.

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 Philips In.Sight B120/37 baby monitor's cloud-based web interface (Weaved service) contains a stored XSS vulnerability in the 'name' parameter within deviceSettings.php and shareDevice.php. This allows injection of malicious JavaScript that executes when users view device configuration or sharing pages.

MitigationImplement proper input validation and output encoding for the 'name' parameter and all user-supplied inputs. Apply context-aware sanitization and consider implementing Content Security Policy headers to prevent script execution.

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
In.sight B120\\37Hardware / appliance
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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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. Confirm device model
    Identify the Philips In.Sight B120/37 baby monitor in your environment by checking device labels, network inventory, or management interfaces. This device must be present for the CVE to apply.
    Affected if The device model is Philips In.Sight B120/37
  2. Verify Weaved service is active
    Check if the baby monitor is configured to use the Weaved cloud-based remote access service. This is typically enabled during initial device setup and creates a web accessible endpoint at weaved.com or similar URLs.
    Affected if The device uses Weaved for cloud access and the web interface is reachable over the internet
  3. Access deviceSettings.php endpoint
    Navigate to the Weaved web interface for the device and locate the device settings page. This is typically found at a URL path containing 'deviceSettings.php' where device configuration options are displayed.
    Affected if The deviceSettings.php page is accessible and displays device configuration including the 'name' parameter
  4. Inspect the 'name' parameter handling
    Examine how the 'name' field in the device settings is rendered. Look for whether user-supplied characters in the name are reflected back in the page source without encoding or sanitization.
    Affected if The 'name' parameter value is rendered in HTML without proper encoding, allowing script tag injection
  5. Test for stored XSS in shareDevice.php
    Access the device sharing functionality at 'shareDevice.php' and check if the device name appears in the page output. Attempt to determine if the name value is stored and displayed without sanitization.
    Affected if The shareDevice.php page reflects the device name without output encoding, indicating stored XSS exists

A user is affected if they operate a Philips In.Sight B120/37 baby monitor configured with the Weaved cloud service where the 'name' parameter in deviceSettings.php or shareDevice.php is rendered without proper input sanitization.

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 proper input validation and output encoding for the 'name' parameter and all user-supplied inputs. Apply context-aware sanitization and consider implementing Content Security Policy headers to prevent script execution.

Fix this in In.sight B120\\37 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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