CVE Intelligence
Skip to main content
CRITICALpublic exploit

CVE-2025-49223

CVE-2025-49223 Vulnerability Analysis & Exploit Intelligence

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.

Published Updated Sources: cvelistV5, naver

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

1%

chance of exploitation in 30 days

Affects

naver

billboard_js

CVSS base

9.8

CRITICAL

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

naver

Products (1)

billboard js

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
9.8CVSS 3.1CRITICAL——cvelistV5

Weakness & attack patterns

  • CWE-1321

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

poc in github

References

1 on the record

Elsewhere on this site

  • naverevery CVE for this vendor
  • CWE-1321other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.