CVE-2025-62584VulnerabilityPublished 16 Oct 2025

CVE-2025-62584: NAVER Whale browser · Origin Validation Error

Affects NAVER Whale browserSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.33.325.17 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.33.325.17

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade NAVER Whale browser to 4.33.325.17.

Affected software

Product	Affected	Fixed in
NAVER NAVER Whale browser	Affected <4.33.325.17	Fixed in 4.33.325.17

AI-suggested

Organizations should prioritize updating the NAVER Whale browser to version 4.33.325.17 or later once the patch is released by the vendor. Until then, users should be advised to avoid opening untrusted or suspicious websites in multiple tabs simultaneously within the Whale browser. Implementing browser usage policies that restrict or monitor Whale browser deployment can reduce exposure. Network-level controls such as web filtering and endpoint security solutions can help detect and block malicious web content attempting to exploit this vulnerability. Security teams should educate users about the risks of opening unknown links in new tabs and encourage the use of alternative browsers with stronger security track records if Whale is not essential. Monitoring for unusual browser behavior or cross-origin data access attempts can provide early detection. Finally, organizations should engage with NAVER for timely updates and consider sandboxing or isolating Whale browser sessions in high-risk environments.

Description

Whale browser before 4.33.325.17 allows an attacker to bypass the Same-Origin Policy in a dual-tab environment.

Impact

For European organizations, this vulnerability poses a significant risk to data confidentiality and integrity, especially for those relying on the NAVER Whale browser for web access. Attackers could exploit this flaw to steal sensitive corporate information, session tokens, or perform unauthorized actions on behalf of users by leveraging cross-origin data access. This is particularly concerning for sectors handling sensitive personal data, financial information, or intellectual property. The vulnerability could facilitate targeted attacks such as phishing or corporate espionage. Given the browser’s niche market share in Europe, the impact may be limited to organizations or users who have adopted Whale, but those affected could face serious data breaches or compliance violations under GDPR. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability becomes widely known. The dual-tab requirement means user behavior influences exploitability, but the risk remains relevant in typical browsing scenarios.

CWE-346Origin Validation Error (opens in a new tab)
Class weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not properly verify that the source of data or communication is valid.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Exploit Script-Based APIs (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cve.naver.com/detail/cve-2025-62584.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 07:17 UTC

WeaknessesCWE-346

Technical details

References

Community reviews

Related threats