Skip to main content
VulnerabilityPublished

CVE-2025-49223: NAVER billboard.js · Prototype Pollution

Affects NAVER billboard.jsSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.15.1 as a priority.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.15.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade NAVER billboard.js to 3.15.1.

Affected software

ProductAffectedFixed in
npmbillboard.jspkg:npm/billboard.jsOther threatsAffected
  • <3.15.1
Fixed in
  • 3.15.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take the following specific mitigation steps: 1) Immediately identify all instances of billboard.js in their web applications and verify the version in use. 2) Upgrade all affected instances to version 3.15.1 or later, where the vulnerability is patched. 3) If immediate upgrade is not feasible, implement temporary mitigations such as input validation and sanitization to prevent malicious payloads from reaching the 'generate' function. 4) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the risk of code injection. 5) Conduct thorough code reviews and penetration testing focusing on prototype pollution vectors in JavaScript components. 6) Monitor application logs and network traffic for unusual activity indicative of exploitation attempts. 7) Educate development teams about prototype pollution risks and secure coding practices to prevent similar vulnerabilities. 8) Maintain an inventory of third-party libraries and establish a patch management process to ensure timely updates.

Description

billboard.js before 3.15.1 was discovered to contain a prototype pollution via the function generate, which could allow attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…