VulnerabilityPublished 4 Jul 2025Updated 8 Jul 2025

CVE-2025-53600: 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.32.315.22 soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

7.5High

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

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

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 4 Jul 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 26 Oct 2026.

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 or the CVSS exploit maturity 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.32.315.22.

Affected software

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

AI-suggested

Immediate mitigation involves advising users and organizations to upgrade NAVER Whale browser to version 4.32.315.22 or later once the patch is released. Until then, users should consider switching to alternative browsers with robust SOP enforcement.
Implement network-level controls such as web filtering to restrict access to untrusted or suspicious websites that could exploit this vulnerability.
Employ Content Security Policy (CSP) headers on web applications to limit the execution of unauthorized scripts and reduce the risk of cross-origin attacks.
Educate users about the risks of using niche browsers for sensitive activities and encourage adherence to corporate browser policies.
Monitor network traffic and browser behavior for anomalies indicative of cross-origin attacks or session manipulation.
For organizations developing web applications, conduct thorough testing against SOP bypass scenarios and reinforce origin validation logic on the server side to prevent unauthorized requests.

Description

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

Impact

For European organizations, this vulnerability poses a substantial risk, particularly for those using NAVER Whale browser in environments where sensitive web applications are accessed. The ability to bypass the Same-Origin Policy can lead to unauthorized manipulation of web sessions, data theft, or injection of malicious scripts, compromising the integrity of web-based workflows. Organizations in sectors such as finance, healthcare, and government, where data integrity is paramount, could face targeted attacks exploiting this flaw. Additionally, multinational companies with Korean business relations or employees using Whale browser may inadvertently expose their internal systems to cross-origin attacks. The vulnerability could also facilitate advanced phishing or social engineering attacks by allowing attackers to present manipulated content from trusted origins. Given the browser’s niche but growing user base, the impact is moderate but focused, with potential for escalation if combined with other vulnerabilities or social engineering tactics.

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-53600.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 21:18 UTC

WeaknessesCWE-346

Technical details

References

Community reviews

Related threats