Skip to main content
VulnerabilityPublished Updated

CVE-2026-1513: NAVER billboard.js · Cross-site Scripting

Affects NAVER billboard.jsSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium : upgrade to 3.18.0 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jan 2026

  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.18.0.

Affected software

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

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

AI-suggested

  1. Upgrade all instances of billboard.js to version 3.18.0 or later where the vulnerability is fixed.
  2. Implement strict input validation and sanitization on all user-supplied data before it is passed to billboard.js to prevent injection of malicious scripts.
  3. Apply Content Security Policy (CSP) headers to restrict the execution of untrusted scripts and reduce the impact of potential XSS attacks.
  4. Conduct code reviews and security testing focusing on client-side libraries and their integration points.
  5. Educate developers on secure coding practices related to JavaScript and third-party libraries.
  6. Monitor web application logs for unusual activity or signs of attempted exploitation.
  7. If upgrading immediately is not feasible, consider temporarily disabling or limiting features that accept user input for chart options.
  8. Use web application firewalls (WAFs) with rules to detect and block XSS payloads targeting billboard.js.

Description

billboard.js before 3.18.0 allows an attacker to execute malicious JavaScript due to improper sanitization during chart option binding.

References

Community reviews

Loading reviews…