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

Plugin security history

PHP Everywhere Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with PHP Everywhere, published between 2022 and 2022.

Dataset last synchronized: 2026-08-02 09:41:47 UTC

At a glance

Security Snapshot

4Total records
3Critical
1High
0Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2022-01-04First disclosure
2022-01-13Latest disclosure
4 of 4CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202244 records

Severity Breakdown

SeverityRecordsShare
Critical375%
High125%

Vulnerability-Type Breakdown

Other

3 records75%

First: 2022. Latest: 2022.

CSRF

1 record25%

First: 2022. Latest: 2022.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

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

Latest Known Patched Versions

  • 2.0.3
  • 3.0.0

Affected-Version History

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

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-2.0.2PHP Everywhere <= 2.0.2 - Cross-Site Request ForgeryJanuary 13, 20222.0.3High
*-2.0.3PHP Everywhere <= 2.0.3 - Remote Code Execution by Subscriber+ users via shortcodeJanuary 4, 20223.0.0Critical
*-2.0.3PHP Everywhere <= 2.0.3 - Authenticated (Contributor+) Remote Code Execution via MetaboxJanuary 4, 20223.0.0Critical
*-2.0.3PHP Everywhere <= 2.0.3 - Remote Code Execution by Contributor+ users via gutenberg blockJanuary 4, 20223.0.0Critical

Selected source records

Latest Records

HighCVE-2021-23227

PHP Everywhere <= 2.0.2 - Cross-Site Request Forgery

Published: January 13, 2022

Affected versions
*-2.0.2
Patched versions
2.0.3
Original Wordfence record
CriticalCVE-2022-24665

PHP Everywhere <= 2.0.3 - Remote Code Execution by Contributor+ users via gutenberg block

Published: January 4, 2022

Affected versions
*-2.0.3
Patched versions
3.0.0
Original Wordfence record
CriticalCVE-2022-24664

PHP Everywhere <= 2.0.3 - Authenticated (Contributor+) Remote Code Execution via Metabox

Published: January 4, 2022

Affected versions
*-2.0.3
Patched versions
3.0.0
Original Wordfence record
CriticalCVE-2022-24663

PHP Everywhere <= 2.0.3 - Remote Code Execution by Subscriber+ users via shortcode

Published: January 4, 2022

Affected versions
*-2.0.3
Patched versions
3.0.0
Original Wordfence record

Highest-Severity Records

CriticalCVE-2022-24665

PHP Everywhere <= 2.0.3 - Remote Code Execution by Contributor+ users via gutenberg block

Published: January 4, 2022

Affected versions
*-2.0.3
Patched versions
3.0.0
Original Wordfence record
CriticalCVE-2022-24664

PHP Everywhere <= 2.0.3 - Authenticated (Contributor+) Remote Code Execution via Metabox

Published: January 4, 2022

Affected versions
*-2.0.3
Patched versions
3.0.0
Original Wordfence record
CriticalCVE-2022-24663

PHP Everywhere <= 2.0.3 - Remote Code Execution by Subscriber+ users via shortcode

Published: January 4, 2022

Affected versions
*-2.0.3
Patched versions
3.0.0
Original Wordfence record
HighCVE-2021-23227

PHP Everywhere <= 2.0.2 - Cross-Site Request Forgery

Published: January 13, 2022

Affected versions
*-2.0.2
Patched versions
2.0.3
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