LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1513: billboard.js before 3.18.0 allows an attacker to execute malicious JavaScript due to improper sanitization...

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

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1513 is a cross-site scripting issue in NAVER billboard.js. If an application binds untrusted data into chart options, a user could be tricked into running attacker-supplied JavaScript in their browser. The issue is rated medium, but impact depends on where billboard.js is used and whether chart inputs are user-controlled.

Executive priority

Prioritize review for internet-facing applications, customer portals, dashboards, or admin tools that render charts from dynamic data. This is not a confirmed mass-exploitation emergency, but XSS can affect users, sessions, and trust in web applications.

Technical view

The CVE describes improper sanitization during chart option binding in billboard.js before 3.18.0, mapped to CWE-79. CVSS 3.1 is 6.1: network exploitable, low complexity, no privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Organizations are likely exposed where web applications include billboard.js versions described by the advisory and pass user-controlled or externally sourced values into chart configuration or option binding. Exposure is lower for internal-only charts using trusted static data.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV in the supplied bundle. Successful exploitation requires user interaction and a vulnerable application context where malicious chart-related input can reach option binding.

Researcher notes

There is a minor data inconsistency in the provided bundle: the description says “before 3.18.0,” while the affected version entry lists 3.18.0. Treat the vendor advisory as authoritative and verify exact version ranges before closure.

Mitigation direction

  • Inventory applications using billboard.js.
  • Check installed billboard.js version against the NAVER advisory.
  • Upgrade to a non-affected release if vendor guidance confirms availability.
  • Avoid binding untrusted input into chart options.
  • Apply output sanitization and content security policy where appropriate.

Validation and detection

  • Review package manifests and bundled frontend assets for billboard.js.
  • Identify chart option values sourced from users, URLs, APIs, or CMS content.
  • Confirm whether deployed versions are before 3.18.0 per the CVE description.
  • Check vendor advisory for exact affected and fixed version details.
  • Test fixes in staging for chart rendering and security regressions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1513 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2026-1513Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NAVERbillboard.js3.18.0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.