dbcve.org
PublisherApplication · Microsoft

CVE-2013-1327

HIGH · 9.3 CVSS v2.0 Published 2013-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Integer signedness error in Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher file that triggers an improper memory allocation, aka "Publisher Signed Integer Vulnerability."

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

CVE-2013-1327 is an integer signedness error in Microsoft Publisher 2003 SP3 that allows remote code execution when processing a specially crafted .pub file. The vulnerability triggers improper memory allocation due to the signedness issue, enabling attackers to execute arbitrary code via malicious file opening.

MitigationApply Microsoft Security Bulletin MS13-042 (KB2810047) to patch Publisher 2003 SP3, or upgrade to a supported version of Microsoft Office/Publisher. If the software is deprecated, remove it from affected systems.

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
PublisherApplication
Affected:= 2003

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

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 Microsoft Publisher 2003 is installed
    Open Windows Control Panel, navigate to Programs and Features (or Add/Remove Programs), and look for Microsoft Office Publisher 2003 in the installed programs list. Alternatively, check if .pub files are associated with Publisher on the system.
    Affected if Microsoft Publisher 2003 appears in the installed programs list or .pub files are associated with Publisher 2003.
  2. Verify the exact Publisher 2003 version
    If Publisher 2003 is installed, determine the full version number. In Windows, right-click the Publisher program shortcut, select Properties, and check the version field, or open Publisher and go to Help > About Microsoft Office Publisher to see the version and service pack information.
    Affected if The installed version is Microsoft Publisher 2003 (any sub-version, since the CVE specifies = 2003 as affected).
  3. Confirm the service pack level
    Check if Microsoft Publisher 2003 Service Pack 3 is applied. In the About dialog (Help > About Microsoft Office Publisher), look for indication of SP3. If the system has automatic updates enabled, check Windows Update history for KB2810047 installation, which was the patch for this vulnerability.
    Affected if Publisher 2003 is at Service Pack 3 or earlier. The vulnerability specifically affects SP3, so any version at or below SP3 is potentially vulnerable.
  4. Identify active .pub file handling
    Check if .pub file association is present and functional. In Windows Explorer, any .pub file will display the Publisher icon and will open with Publisher 2003 when double-clicked. This confirms the vulnerable component is accessible.
    Affected if The system has .pub file type registered and Publisher 2003 can open these files, meaning the vulnerable parsing code is present and reachable.

A system is affected if Microsoft Publisher 2003 is installed and can open .pub files, regardless of specific subversion, since the vulnerability affects the entire version 2003.

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

Apply Microsoft Security Bulletin MS13-042 (KB2810047) to patch Publisher 2003 SP3, or upgrade to a supported version of Microsoft Office/Publisher. If the software is deprecated, remove it from affected systems.

Recommended fix High confidence

Microsoft 365 Apps or Office 2021/2019 (supported versions with Publisher component)

  1. 1. Back up all important data and Publisher files before making any changes
  2. 2. Since Microsoft Publisher 2003 is end-of-life and no longer receives security updates, upgrade to a supported version of Microsoft Office (such as Microsoft 365 Apps, Office 2021, or Office 2019)
  3. 3. Install the newer Microsoft Office version which includes an updated version of Publisher
  4. 4. After installation, verify that Publisher launches without errors
  5. 5. Test any existing .pub files to ensure they open correctly in the new version
  6. 6. Remove Microsoft Publisher 2003 from the system if still present
Caveat Legacy .pub files from older Publisher versions may need conversion; some features or file compatibility may differ in newer versions; subscription required for Microsoft 365

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

Fix this in Publisher Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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