LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1327: Integer signedness error in Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code...

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."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-1327 is a remote code execution flaw in Microsoft Publisher 2003 SP3. A malicious Publisher file could trigger unsafe memory handling and let an attacker run code on a vulnerable workstation. Business risk is highest where legacy Publisher remains installed and users can receive or open untrusted Publisher documents. Exposure appears limited to environments running Microsoft Publisher 2003 SP3 or systems that still process Publisher files with that version. Prioritize legacy desktop inventories, document-handling workflows, email attachments, shared drives, and any asset records showing Publisher 2003 SP3. Treat this as a legacy-software cleanup and exposure-reduction issue. It enables code execution, but the provided evidence does not show current active exploitation. Priority should be high where Publisher 2003 SP3 still exists or where users handle external Publisher files. Mitigation focus: Review Microsoft MS13-042 and apply the vendor-recommended security update or guidance.; Remove or upgrade Publisher 2003 SP3 where business use is no longer required.; Restrict opening Publisher files from email, web downloads, or untrusted shares..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-1327 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.