Naver Corporation's vulnerability footprint spans a focused but notably prominent portfolio of web development tools, performance-testing platforms, and security libraries widely adopted in enterprise and open-source ecosystems. Vulnerabilities affecting the vendor skew strongly toward critical-severity outcomes, concentrated in products such as nGrinder, Cloud Explorer, and the Lucy XSS Filter, reflecting the vendor's presence in both infrastructure and client-side security layers. The recurring weakness classes center on deserialization of untrusted data, cross-site scripting, sensitive information exposure, and missing authorization controls, which are characteristic of web and middleware software handling user input and maintaining privilege boundaries. Defenders should prioritize this vendor's advisories given the severity profile and the embedded role these tools play in development and deployment pipelines; current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Naver Corporation over time
Of all the CVEs published by Naver Corporation as a CNA, 47.5% affect products that Naver Corporation develops as a vendor.
Of all the CVEs published that affect products developed by Naver Corporation, 79.2% are self-published by Naver Corporation as a CNA.
Signals from CVEs in this vendor scope (24 CVEs).
24 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-33592CRITICAL NAVER Toolbar before 4.0.30.323 allows remote attackers to execute arbitrary code via a crafted upgrade.xml file. Special characters in filename parameter can be the cause of bypas | Jul 19, 2021 | 9.8 | 32 | NO | NO |
CVE-2025-49223CRITICAL 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 Ser | Jun 4, 2025 | 9.8 | 30 | NO | NO |
CVE-2024-28212CRITICAL nGrinder before 3.5.9 uses old version of SnakeYAML, which could allow remote attacker to execute arbitrary code via unsafe deserialization. | Mar 7, 2024 | 9.8 | 30 | NO | NO |
CVE-2020-9752CRITICAL Naver Cloud Explorer before 2.2.2.11 allows the attacker can move a local file in any path on the filesystem as a system privilege through its named pipe. | Mar 23, 2020 | 9.8 | 29 | NO | NO |
CVE-2020-9753CRITICAL Whale Browser Installer before 1.2.0.5 versions don't support signature verification for Flash installer. | May 20, 2020 | 9.1 | 28 | NO | NO |
CVE-2020-9751CRITICAL Naver Cloud Explorer before 2.2.2.11 allows the system to download an arbitrary file from the attacker's server and execute it during the upgrade. | Mar 3, 2020 | 9.1 | 28 | NO | NO |
CVE-2021-33591HIGH An exposed remote debugging port in Naver Comic Viewer prior to 1.0.15.0 allowed a remote attacker to execute arbitrary code via a crafted HTML page. | May 28, 2021 | 8.8 | 27 | NO | NO |
CVE-2024-28213CRITICAL nGrinder before 3.5.9 allows to accept serialized Java objects from unauthenticated users, which could allow remote attacker to execute arbitrary code via unsafe Java objects deser | Mar 7, 2024 | 9.8 | 26 | NO | NO |
CVE-2024-28211CRITICAL nGrinder before 3.5.9 allows connection to malicious JMX/RMI server by default, which could be the cause of executing arbitrary code via RMI registry by remote attacker. | Mar 7, 2024 | 9.8 | 26 | NO | NO |
CVE-2022-24077HIGH Naver Cloud Explorer Beta allows the attacker to execute arbitrary code as System privilege via malicious DLL injection. | Jun 13, 2022 | 7.8 | 24 | NO | NO |
Signals from CVEs in this vendor scope (24 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Naver Corporation.
Media articles that mention a CVE ID that affects a product developed by Naver Corporation — matched by CVE ID, not by vendor name.