Advisories
This weekExploitable · Confirmed

xml2js: xml2js is vulnerable to prototype pollution

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

xml2js (npm)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • xml2js (npm): every version, before 0.5.0

The fix

  • xml2js (npm) fixed in 0.5.0

    npm
    npm install xml2js@0.5.0
    pnpm
    pnpm add xml2js@0.5.0
    yarn
    yarn add xml2js@0.5.0
    bun
    bun add xml2js@0.5.0
    Check what is installed
    npm ls xml2js
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency xml2js to 0.5.0 or the nearest later release, to fix CVE-2023-0842. 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

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))