How severe is CVE-2010-2571?

CVE-2010-2571 has a CVSS 2.0 base score of 9.3, rated critical severity.

Is CVE-2010-2571 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 22% (97th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2010-2571?

CVE-2010-2571 primarily affects Microsoft Publisher. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2010-2571?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2010-2571 published?

CVE-2010-2571 was published on 2010-12-16 and last updated on 2026-06-16.

CVE-2010-2571

CVE-2010-2571 is a critical-severity vulnerability in Microsoft Publisher with a CVSS 2.0 base score of 9.3. Its EPSS exploit-prediction score of 22% places it in the 97th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-20.

Key facts

Severity: Critical (CVSS 2.0 base score 9.3)
EPSS exploit prediction: 22% (97th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-20
Affected product: Microsoft Publisher
Published: 2010-12-16
Last modified: 2026-06-16

Description

Array index error in pubconv.dll (aka the Publisher Converter DLL) in Microsoft Publisher 2002 SP3 and 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher 97 file, aka "Memory Corruption Due To Invalid Index Into Array in Pubconv.dll Vulnerability."

Frequently asked questions

What is CVE-2010-2571?: Array index error in pubconv.dll (aka the Publisher Converter DLL) in Microsoft Publisher 2002 SP3 and 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher 97 file, aka "Memory Corruption Due To Invalid Index Into Array in Pubconv.dll Vulnerability."
How severe is CVE-2010-2571?: CVE-2010-2571 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2010-2571 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 22% (97th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-2571?: CVE-2010-2571 primarily affects Microsoft Publisher. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-2571?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2010-2571 published?: CVE-2010-2571 was published on 2010-12-16 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:microsoft:publisher:2002:sp3:*:*:*:*:*:*
cpe:2.3:a:microsoft:publisher:2003:sp3:*:*:*:*:*:*

More vulnerabilities in Microsoft Publisher

CVE-2013-1322 — Critical (CVSS 10.0): Microsoft Publisher 2003 SP3 does not properly check table range data, which allows remote attackers to execute…
CVE-2013-1320 — Critical (CVSS 10.0): Buffer overflow in Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code via a crafted…
CVE-2013-1319 — Critical (CVSS 10.0): Microsoft Publisher 2003 SP3 does not properly check the return value of an unspecified method, which allows remote…
CVE-2013-1318 — Critical (CVSS 10.0): Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher file that…
CVE-2008-0102 — Critical (CVSS 10.0): Unspecified vulnerability in Microsoft Office Publisher 2000, 2002, and 2003 SP2 allows remote attackers to execute…
CVE-2007-1117 — Critical (CVSS 10.0): Unspecified vulnerability in Publisher 2007 in Microsoft Office 2007 allows remote attackers to execute arbitrary code…

All CVEs affecting Microsoft Publisher →

Other CWE-20 (Improper Input Validation) vulnerabilities

CVE-2026-48316 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48281 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48277 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48055 — Critical (CVSS 10.0): Streambert is a cross-platform Electron Desktop App to stream and download any video media. In versions 2.4.0 and…
CVE-2026-34910 — Critical (CVSS 10.0): A malicious actor with access to the network could exploit an Improper Input Validation vulnerability found in UniFi OS…
CVE-2026-33587 — Critical (CVSS 10.0): Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and…

Browse all CWE-20 (Improper Input Validation) vulnerabilities →