This weekExploitable · Confirmed
bassmaster: Arbitrary JavaScript Execution in bassmaster
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
bassmaster (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- bassmaster (npm): every version, before 1.5.2
The fix
bassmaster (npm) fixed in 1.5.2
npmnpm install bassmaster@1.5.2pnpmpnpm add bassmaster@1.5.2yarnyarn add bassmaster@1.5.2bunbun add bassmaster@1.5.2Check what is installednpm ls bassmasterPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency bassmaster to 1.5.2 or the nearest later release, to fix CVE-2014-7205. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
EPSS puts the chance of exploitation in the next 30 days at 79%.
FIRST EPSSStated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)