Php EverywhereWordPress extension · Php Everywhere Project
CVE-2021-23227
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Alexander Fuchs PHP Everywhere plugin <= 2.0.2 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in PHP Everywhere WordPress plugin versions 2.0.2 and below allows attackers to trick authenticated administrators into performing unintended administrative actions through maliciously crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Php EverywhereWordPress extension
<= 2.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify PHP Everywhere plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'PHP Everywhere' in the listAffected if PHP Everywhere plugin appears in the installed plugins list
-
Check installed PHP Everywhere versionIn the Plugins list, locate PHP Everywhere and view the version number displayed below the plugin name, or check the plugin header in wp-content/plugins/php-everywhere/php-everywhere.phpAffected if The version number displayed is 2.0.2 or lower (e.g., 2.0.2, 2.0.1, 2.0.0, 1.x.x)
-
Confirm plugin is activeIn WordPress admin > Plugins, check if PHP Everywhere shows as 'Active' under the plugin statusAffected if PHP Everywhere is activated and running on the site
-
Review admin function nonce implementationExamine the plugin source code in wp-content/plugins/php-everywhere/ for admin action handlers (typically in files like admin.php or within class files). Look forwp_nonce_field() or check_admin_referer() calls in functions that handle admin form submissionsAffected if Admin functions that process requests lack proper WordPress nonce verification (wp_nonce_field or check_admin_referer)
Your environment is affected if PHP Everywhere plugin version 2.0.2 or lower is installed and active, and admin functions lack CSRF token validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate PHP Everywhere plugin to version 2.0.3 or later to obtain the patched version. Additionally, ensure WordPress anti-CSRF tokens (nonces) are properly implemented in plugin admin functions.
Fix this in Php Everywhere
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23227 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-23227 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data