CVE-2025-62584
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhale browser before 4.33.325.17 allows an attacker to bypass the Same-Origin Policy in a dual-tab environment.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Same-Origin Policy (SOP) bypass vulnerability in the Whale browser. The vulnerability allows an attacker in a dual-tab environment to circumvent the browser's origin isolation, potentially enabling unauthorized access to data or functionality across different origins that should normally be separated.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.33.325.17CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Navercorp Whale browser is installedLocate the Whale browser application on the system. On Windows, check Program Files or the user's application folder for 'Whale' or 'Naver Whale' directory. On macOS, check the Applications folder for Whale.app.Affected if Whale browser application exists on the system
-
Determine the installed Whale browser versionOpen Whale browser and navigate to the About page (typically Whale menu > About Whale or whale://version). Alternatively, right-click the Whale executable file and select Properties to view the file version information.Affected if The displayed version number is less than 4.33.325.17
-
Verify the version against the affected rangeCompare your installed version to the vulnerable range: any version below 4.33.325.17 is affected. Note that version numbers follow the format major.minor.build.patch.Affected if The installed version falls below 4.33.325.17 in the version sequence
If Navercorp Whale browser is installed and its version is lower than 4.33.325.17, the environment is vulnerable to the SOP bypass described in CVE-2025-62584.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.33.325.17
Update Whale browser to version 4.33.325.17 or later to obtain the patched version that addresses this SOP bypass.
4.33.325.17
- Open Whale browser and navigate to Settings > About Whale to check the current version number
- If the version is below 4.33.325.17, click the 'Update' button if available, or download the latest Whale browser from the official Whale website (whale.naver.com)
- Restart the browser after the update completes
- Verify the installed version is 4.33.325.17 or higher by returning to Settings > About Whale
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62584 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data