CVE-2013-1319
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method,...
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method, which allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Publisher Return Value Handling Vulnerability."
Exploit likelihood
What each source reports
NVD Score used
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method, which allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Publisher Return Value Handling Vulnerability."
- Record
CVE-2013-1319- CVSS 2.0
- 10.0 High
AV:N/AC:L/Au:N/C:C/I:C/A:C - Updated
- 2026-11-02
CVE List No score
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method, which allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Publisher Return Value Handling Vulnerability."
- Record
CVE-2013-1319- Updated
- 2026-11-02
EUVDEUVD-2013-1359 No score
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method, which allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Publisher Return Value Handling Vulnerability."
- Record
EUVD-2013-1359- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-97qc-chmq-2h4c No score
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method,...
Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method, which allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Publisher Return Value Handling Vulnerability."
- Record
GHSA-97qc-chmq-2h4c- 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-1319 is a high vulnerability (CVSS 10.0) 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 25.1%, the 97th percentile. No source names a fixed version.