CVE-2013-1327
Integer signedness error in Microsoft Publisher 2003 SP3 allows remote attackers to execute...
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."
Exploit likelihood
What each source reports
NVD Score used
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."
- Record
CVE-2013-1327- CVSS 2.0
- 9.3 High
AV:N/AC:M/Au:N/C:C/I:C/A:C - Weakness
- CWE-189
- Updated
- 2026-11-02
CVE List No score
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."
- Record
CVE-2013-1327- Updated
- 2026-11-02
EUVDEUVD-2013-1367 No score
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."
- Record
EUVD-2013-1367- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-7qhg-62h8-j958 No score
Integer signedness error in Microsoft Publisher 2003 SP3 allows remote attackers to execute...
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."
- Record
GHSA-7qhg-62h8-j958- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2013-1327 is a high vulnerability (CVSS 9.3) in Microsoft Publisher, published May 15, 2013. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 20.8%, the 97th percentile. No source names a fixed version.