Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

article2pdf Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 2 vulnerability records associated with article2pdf, published between 2019 and 2019.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

2Total records
1Critical
1High
0Medium
0Low
0Informational
0Patched records
2Currently marked unpatched
2019-03-26First disclosure
2019-03-29Latest disclosure
2 of 2CVE coverage

Use this history

Check and watch article2pdf.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
201922 records

Severity Breakdown

SeverityRecordsShare
Critical150%
High150%

Vulnerability-Type Breakdown

Information Disclosure

1 record50%

First: 2019. Latest: 2019.

Other

1 record50%

First: 2019. Latest: 2019.

Patch Status

Patched
0
Currently marked unpatched
2
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

No patched version values are available for this software in the current Production Feed records.

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
0.27article2pdf <= 0.27 - Denial of ServiceMarch 29, 2019Not suppliedHigh
0.26article2pdf <= 0.27 - Denial of ServiceMarch 29, 2019Not suppliedHigh
0.25article2pdf <= 0.27 - Denial of ServiceMarch 29, 2019Not suppliedHigh
0.24article2pdf <= 0.27 - Denial of ServiceMarch 29, 2019Not suppliedHigh
0.27article2pdf 0.24 - 0.27 - Information DisclosureMarch 26, 2019Not suppliedCritical
0.26article2pdf 0.24 - 0.27 - Information DisclosureMarch 26, 2019Not suppliedCritical
0.25article2pdf 0.24 - 0.27 - Information DisclosureMarch 26, 2019Not suppliedCritical
0.24article2pdf 0.24 - 0.27 - Information DisclosureMarch 26, 2019Not suppliedCritical

Selected source records

Latest Records

HighCVE-2019-1000031

article2pdf <= 0.27 - Denial of Service

Published: March 29, 2019

Affected versions
0.24; 0.25; 0.26; 0.27
Patched versions
Not supplied
Original Wordfence record
CriticalCVE-2019-1010257

article2pdf 0.24 - 0.27 - Information Disclosure

Published: March 26, 2019

Affected versions
0.24; 0.25; 0.26; 0.27
Patched versions
Not supplied
Original Wordfence record

Highest-Severity Records

CriticalCVE-2019-1010257

article2pdf 0.24 - 0.27 - Information Disclosure

Published: March 26, 2019

Affected versions
0.24; 0.25; 0.26; 0.27
Patched versions
Not supplied
Original Wordfence record
HighCVE-2019-1000031

article2pdf <= 0.27 - Denial of Service

Published: March 29, 2019

Affected versions
0.24; 0.25; 0.26; 0.27
Patched versions
Not supplied
Original Wordfence record

Currently Marked Unpatched Records

HighCVE-2019-1000031

article2pdf <= 0.27 - Denial of Service

Published: March 29, 2019

Affected versions
0.24; 0.25; 0.26; 0.27
Patched versions
Not supplied
Original Wordfence record
CriticalCVE-2019-1010257

article2pdf 0.24 - 0.27 - Information Disclosure

Published: March 26, 2019

Affected versions
0.24; 0.25; 0.26; 0.27
Patched versions
Not supplied
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory