dbcve.org
OfficeApplication · Microsoft

CVE-2007-6329

MEDIUM · 6.4 CVSS v2.0 Published 2007-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
Microsoft Office 2007 12.0.6015.5000 and MSO 12.0.6017.5000 do not sign the metadata of Office Open XML (OOXML) documents, which makes it easier for remote attackers to modify Dublin Core metadata fields, as demonstrated by the (1) LastModifiedBy and (2) creator fields in docProps/core.xml in the OOXML ZIP container.

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

Microsoft Office 2007 versions 12.0.6015.5000 and 12.0.6017.5000 do not cryptographically sign the Dublin Core metadata in Office Open XML (OOXML) documents. Since OOXML documents are ZIP containers containing docProps/core.xml, attackers can modify fields like LastModifiedBy and creator without detection, enabling document attribution tampering and potential forensic manipulation.

MitigationImplement document integrity validation processes or digital signature verification for OOXML documents to detect unauthorized metadata modifications. Alternatively, upgrade to Microsoft Office versions that address this vulnerability.

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
OfficeApplication
Affected:= 2007

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/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 Microsoft Office version
    Open any Office application (Word, Excel, PowerPoint), go to File > Help, and locate the version information under 'About Microsoft Office [Application]'. Look for the exact build number.
    Affected if The build number matches 12.0.6015.5000 or 12.0.6017.5000, indicating Microsoft Office 2007 at these specific vulnerable builds.
  2. Confirm document type in use
    Identify if you create, edit, or process Office Open XML (OOXML) documents, which have file extensions .docx (Word), .xlsx (Excel), or .pptx (PowerPoint).
    Affected if You work with .docx, .xlsx, or .pptx files, as these OOXML documents contain the unsigned Dublin Core metadata in their ZIP container structure.
  3. Inspect document metadata structure
    Rename an OOXML document file to have a .zip extension, then open the archive and examine the docProps/core.xml file. This XML file contains Dublin Core fields such as LastModifiedBy and creator.
    Affected if The core.xml file exists and contains metadata fields without any cryptographic signature or integrity verification mechanism present.
  4. Check for digital signature presence
    In Office, open an OOXML document, go to File > Prepare > View Signatures, or inspect the document's digital signature status. Also check if the _xmlsignatures folder exists within the document archive.
    Affected if No digital signatures are applied to the document or the Dublin Core metadata specifically, confirming the vulnerability is exploitable.

You are affected if you use Microsoft Office 2007 at build 12.0.6015.5000 or 12.0.6017.5000 and work with OOXML documents (.docx, .xlsx, .pptx), as the Dublin Core metadata in docProps/core.xml lacks cryptographic signing.

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

Implement document integrity validation processes or digital signature verification for OOXML documents to detect unauthorized metadata modifications. Alternatively, upgrade to Microsoft Office versions that address this vulnerability.

Fix this in Office Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-6329 — 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-2007-6329 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