The vulnerability of the logfile parameter in the lib/Local.js library of the npm package browserstack-local for the Node.js software platform allows a hacker to execute any command they desire.

The vulnerability of the logfile parameter in the lib/Local.js library of the npm package browserstack-local for the Node.js software platform is related to improper code generation management. Exploiting this vulnerability could allow an attacker to execute arbitrary commands...

CVE-2025-57283

A flaw was found in browserstack-local. Improper input sanitization of the logfile variable allows an attacker to inject arbitrary OS commands that are executed when this variable is processed, resulting in arbitrary command execution. Mitigation To mitigate this issue, implement strict input...

GHSA-G4W6-C99W-4WH7 BrowserStack Local vulnerable to Command Injection through logfile variable

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

BrowserStack Local vulnerable to Command Injection through logfile variable

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

@1studio/ui (>=2.17.0, <=2.83.0), @elliemae/pui-e2e-test-sdk (>=0.1.0, <=7.3.4) +8 more potentially affected by CVE-2025-57283 via browserstack-local (>=1.3.0, <=1.5.4)

browserstack-local NPM version =1.3.0, =2.17.0, =0.1.0, =1.0.0, =5.0.0-beta.13, =1.13.0, =0.1.0, =3.0.2, =1.0.28-beta.9, =0.1.0, =1.0.576, =1.0.585 Source cves: CVE-2025-57283 Source advisory: OSV:GHSA-G4W6-C99W-4WH7...

CVE-2025-57283

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

CVE-2025-57283

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

EUVD-2025-206491

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

CVE-2025-57283

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

PT-2026-5132

Name of the Vulnerable Software and Affected Versions browserstack-local version 1.5.8 Description The Node.js package browserstack-local is affected by a command injection issue. The problem stems from insufficient sanitization of the logfile variable within the lib/Local.js file, potentially...

browserstack-cypress-cli (>=1.14.1, <=1.36.3) potentially affected by CVE-2025-57283 via browserstack-local (>=1.5.1, <=1.5.4)

browserstack-local NPM version =1.5.1, =1.14.1, =1.36.3 Source cves: CVE-2025-57283 Source advisory: SNYK:JS-BROWSERSTACKLOCAL-15149317...

Command Injection

Overview browserstack-local is a Nodejs bindings for BrowserStack Local Affected versions of this package are vulnerable to Command Injection via the logfile variable in lib/Local.js. An attacker can execute arbitrary operating system commands by supplying crafted input to this variable. This is...

CVE-2025-57283: Improper Control of Generation of Code

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

CVE-2025-57283

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

CVE-2025-57283

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...

CVE-2025-57283

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js...