# CVE-2026-1513: billboard.js is vulnerable to XSS during chart option binding

> An attacker can execute malicious JavaScript via improper sanitization in chart option binding, affecting users of the billboard.js library.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-rpc5-pm7q-hjmp

## What is CVE-2026-1513?

CVE-2026-1513 is a medium-severity cross-site scripting vulnerability in NAVER billboard.js, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-1513?

2 open source packages ship an affected version, including billboard.js. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `billboard.js` | npm | All versions | 3.18.0 |
| `billboard.js` | npm | All versions | 3.18.0 |

Products: Naver Billboard.js.

## How do I fix CVE-2026-1513?

Upgrade billboard.js to 3.18.0 or later.

## Is CVE-2026-1513 being exploited?

There is no known exploitation of CVE-2026-1513 in the wild and no public exploit code.

## Other vulnerabilities in NAVER billboard.js

- [CVE-2025-49223](https://insights.sbomify.com/CVE-2025-49223/): billboard.js allows prototype pollution via the function generate (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1513 and fix it if it is affected.

What it is: CVE-2026-1513 is a medium-severity cross-site scripting vulnerability in NAVER billboard.js, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1513 in the wild and no public exploit code.

Affected packages and fixed versions:
- billboard.js (npm): affected all versions; fixed in 3.18.0
- billboard.js (npm): affected all versions; fixed in 3.18.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1513/ (Markdown: https://insights.sbomify.com/CVE-2026-1513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1513
- OSV: https://osv.dev/vulnerability/CVE-2026-1513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1513/
Summaries are generated and may contain mistakes; the official description above is the record.