WhaleApplication · Navercorp

CVE-2025-69234

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-30
Fix available
A fix is available. Upgrade to 4.35.351.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Whale browser before 4.35.351.12 allows an attacker to escape the iframe sandbox in a sidebar 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 confidence

Whale browser before version 4.35.351.12 contains a sandbox escape vulnerability in its sidebar environment that allows an attacker to break out of iframe sandbox restrictions. This critical flaw (CVSS 9.1) enables potentially malicious web content to gain elevated privileges within the browser.

MitigationUpgrade Whale browser to version 4.35.351.12 or later to remediate the sandbox escape vulnerability. Until the update is applied, restrict access to untrusted websites and disable sidebar extensions if possible.

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
WhaleApplication
Affected:< 4.35.351.12

CVSS 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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Whale browser is installed
    Check for Whale browser executable in common installation paths (e.g., C:\Program Files\Whale\ or look for Whale in installed programs) or open Whale and navigate to settings to verify the browser identity.
    Affected if Whale browser is not present on the system.
  2. Locate the installed version number
    Open Whale browser, type 'whale://version' in the address bar and press Enter, or go to Settings > About Whale to view the version information.
    Affected if Unable to retrieve version number from the Whale browser installation.
  3. Compare installed version against the vulnerable range
    Take the version number found (e.g., 4.35.351.12) and compare it numerically to the affected range: any version before 4.35.351.12 is vulnerable.
    Affected if The installed version is less than 4.35.351.12 (for example, 4.35.351.0 or 4.34.x.x).
  4. Determine if sidebar environment is in use
    Check if the Whale sidebar feature is enabled: look for a sidebar panel in the Whale browser interface, or check for installed sidebar extensions in Settings > Extensions.
    Affected if The sidebar is actively enabled or sidebar extensions are installed, making exploitation possible if the version is vulnerable.

If Whale browser version is below 4.35.351.12 AND the sidebar environment is enabled or in use, the system is affected by this sandbox escape vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.35.351.12 or later
Fixed in 4.35.351.12
Interim mitigation

Upgrade Whale browser to version 4.35.351.12 or later to remediate the sandbox escape vulnerability. Until the update is applied, restrict access to untrusted websites and disable sidebar extensions if possible.

Recommended fix High confidence

Whale 4.35.351.12 or later

  1. 1. Open Whale browser and navigate to Settings or About page to check the current version number
  2. 2. If the current version is below 4.35.351.12, download and install Whale version 4.35.351.12 or later from the official Whale browser website
  3. 3. After installation, verify the installed version by checking About Whale to confirm the update was successful
  4. 4. Restart the browser to ensure all components are updated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Whale Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69234 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69234 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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