dbcve.org
CWE-346Weakness · CWE-346

CVE-2025-59845

HIGH · 8.2 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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
Apollo Studio Embeddable Explorer & Embeddable Sandbox are website embeddable software solutions from Apollo GraphQL. Prior to Apollo Sandbox version 2.7.2 and Apollo Explorer version 3.7.3, a cross-site request forgery (CSRF) vulnerability was identified. The vulnerability arises from missing origin validation in the client-side code that handles window.postMessage events. A malicious website can send forged messages to the embedding page, causing the victim’s browser to execute arbitrary GraphQL queries or mutations against their GraphQL server while authenticated with the victim’s cookies. This issue has been patched in Apollo Sandbox version 2.7.2 and Apollo Explorer version 3.7.3.

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 · high confidence

Apollo Studio Embeddable Explorer and Embeddable Sandbox versions prior to 2.7.2 and 3.7.3 respectively contain a CSRF vulnerability due to missing origin validation in the client-side postMessage event handler. This allows malicious websites to send forged messages that cause the victim's browser to execute arbitrary GraphQL queries or mutations against their authenticated GraphQL server.

MitigationUpgrade to Apollo Sandbox version 2.7.2 or Apollo Explorer version 3.7.3, which include origin validation in the postMessage handler to verify message source before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Identify Apollo GraphQL packages in use
    Search your codebase (package.json, package-lock.json, node_modules) for @apollo/sandbox, @apollo/explorer, or apollo-sandbox packages
    Affected if One of these packages is present in dependencies
  2. Determine installed version
    Locate the specific version number of the Apollo package in your lock file or by running npm list @apollo/sandbox or npm list @apollo/explorer
    Affected if The version is below 2.7.2 for Sandbox or below 3.7.3 for Explorer
  3. Confirm embeddable usage
    Search your frontend code for imports or script tags that load Apollo Sandbox or Explorer components for embedding in web pages (iframe usage, script src references, or component imports)
    Affected if The Apollo tool is loaded and embedded in a web-accessible page
  4. Check postMessage origin validation
    Inspect the Apollo package source code in node_modules for postMessage event handlers and verify if they validate the origin parameter before processing messages
    Affected if The code does not validate the origin in postMessage listeners, allowing messages from any domain
  5. Verify exposure to untrusted origins
    Determine whether the embedded Apollo tool can be reached by websites other than your trusted domains (check iframe src, allowed origins configuration, or CORS settings)
    Affected if The embedded tool is accessible to or can be framed by untrusted websites

You are affected if you have Apollo Sandbox before 2.7.2 or Apollo Explorer before 3.7.3 embedded in a web page, and that page can be accessed by or messaged from untrusted domains.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Apollo Sandbox version 2.7.2 or Apollo Explorer version 3.7.3, which include origin validation in the postMessage handler to verify message source before processing.

Recommended fix High confidence

Apollo Sandbox version 2.7.2 or later; Apollo Explorer version 3.7.3 or later

  1. Identify which Apollo product is in use: Apollo Sandbox or Apollo Explorer
  2. Check the currently installed version of the Apollo product
  3. For Apollo Sandbox users: If version is lower than 2.7.2, upgrade to version 2.7.2 or later
  4. For Apollo Explorer users: If version is lower than 3.7.3, upgrade to version 3.7.3 or later
  5. Verify the upgrade was successful by confirming the new version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59845 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-59845 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