dbcve.org
Office Out Of Box ExperienceApplication · Microsoft

CVE-2025-64677

HIGH · 8.2 CVSS v3.1 Published 2025-12-18
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
Improper neutralization of input during web page generation ('cross-site scripting') in Office Out-of-Box Experience allows an unauthorized attacker to perform spoofing over a network.

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

Cross-site scripting (XSS) vulnerability in Microsoft Office Out-of-Box Experience allows remote attackers to inject malicious scripts into web pages generated during the Office setup process. This can enable session hijacking, credential theft, or spoofing of legitimate content to trick users.

MitigationApply Microsoft security patches for Office when available; consider network-level mitigations such as WAF rules or browser-based XSS protections until vendor patches are deployed.

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
Office Out Of Box ExperienceApplication
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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. Determine if Office setup is currently in progress
    Check for running Office installation processes (e.g., setup.exe, oobecheck.exe, or OfficeClickToRun.exe in setup mode) using Task Manager or command: tasklist /FI "IMAGENAME eq setup.exe" /V
    Affected if Office installation or initial setup wizard is actively running on the machine
  2. Check if Office was recently installed
    Review Windows Event Viewer logs under Application and Services Logs > Microsoft > Office for installation events within the last session, or check Program Files/Microsoft Office for recent installation timestamps
    Affected if Office was installed or repaired in a recent session and OOBE web pages may have been served
  3. Identify OOBE web server port availability
    During a fresh Office installation or repair, run netstat -ano | findstr "2002" or monitor common OOBE ports (typically 2002-2010 range) to see if a local HTTP server is listening
    Affected if A local Office setup web server is bound to a port, indicating OOBE is actively serving web pages that could be exploited
  4. Check installed Office version and update status
    Open any Office app, go to File > Account > About [App] to view the version number, or use: Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" -ErrorAction SilentlyContinue | Select-Object VersionToReport
    Affected if Any version of Office is installed and was set up using the OOBE process (which applies to all versions)
  5. Verify network exposure of OOBE endpoints
    During Office installation, check if the OOBE localhost server is accessible from other machines on the network using: curl http://localhost:2002 or checking firewall rules for Office setup services
    Affected if The OOBE web interface is network-accessible beyond localhost (potential remote attack vector)

This vulnerability affects any environment where the Microsoft Office Out-of-Box Experience is actively running or was recently executed during Office installation, since all versions are impacted.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security patches for Office when available; consider network-level mitigations such as WAF rules or browser-based XSS protections until vendor patches are deployed.

Fix this in Office Out Of Box Experience 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-64677 — 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-64677 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