Loading vulnerability…
CVE-2025-49223 affects billboard.js before version 3.15.1. The vulnerability is a prototype pollution issue in the generate function, where attacker-controlled input can inject arbitrary properties into object prototypes. By polluting the prototype chain, an attacker may alter application behavior in unintended ways, potentially leading to arbitrary code execution in affected application contexts or causing denial of service.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2025-49223, a prototype pollution vulnerability in billboard.js versions <= 3.14.0. The repository contains two files: a README.md with detailed vulnerability and usage information, and an index.html file that serves as the main PoC. The index.html file loads the vulnerable version of billboard.js from a CDN and executes JavaScript code that attempts to pollute Object.prototype using specially crafted payloads with the '__proto__' key. The success of the attack is confirmed via console log messages indicating whether the prototype was polluted. The exploit demonstrates the ability to inject arbitrary properties into all objects, potentially leading to denial of service, logic tampering, or security bypasses in applications using billboard.js. The PoC is operational in a browser environment and does not provide a weaponized or automated attack, but clearly demonstrates the vulnerability's impact.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.