dbcve.org
Php EverywhereWordPress extension · Php Everywhere Project

CVE-2022-24664

HIGH · 8.8 CVSS v3.1 Published 2022-02-16
Fix available
A fix is available. Upgrade to after 2.0.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
PHP Everywhere <= 2.0.3 included functionality that allowed execution of PHP Code Snippets via WordPress metaboxes, which could be used by any user able to edit posts.

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 · high confidence

The PHP Everywhere WordPress plugin <= 2.0.3 allowed execution of arbitrary PHP code through metaboxes without proper authorization checks. Any authenticated user with post-editing capabilities (author, editor, or contributor role) could inject and execute PHP code on the server, leading to potential complete site compromise.

MitigationUpdate PHP Everywhere to version 2.0.4 or later. If immediate update is not possible, disable the plugin and review user roles with edit-post capabilities for suspicious activity.

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
Affected:<= 2.0.3

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify PHP Everywhere plugin installation
    Check your WordPress installation for the presence of the PHP Everywhere plugin in /wp-content/plugins/ or via the WordPress admin Plugins page
    Affected if The plugin directory 'php-everywhere' exists in the plugins folder
  2. Confirm installed plugin version
    View the plugin header comment in the main plugin file (php-everywhere.php) or check the version field on the WordPress Plugins admin page
    Affected if The reported version number is 2.0.3 or lower
  3. Verify plugin is active
    Check the WordPress admin Plugins page or query the wp_options table for the active_plugins option to confirm php-everywhere.php is enabled
    Affected if The plugin shows as 'Active' in WordPress admin or is listed in active plugins
  4. Review user roles with post-editing capabilities
    Navigate to WordPress Users admin page or query wp_usermeta to list users with roles of author, editor, or contributor
    Affected if Any user accounts exist with author, editor, or contributor roles (these roles can trigger the vulnerability)
  5. Inspect for configured PHP code metaboxes
    Check posts/pages for the 'PHP Everywhere' metabox with saved PHP code snippets, or review wp_postmeta for meta_key containing 'php_everywhere'
    Affected if Metaboxes with PHP code are present and saved in the database

Your environment is affected if PHP Everywhere plugin version 2.0.3 or lower is installed and active on your WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.0.3
Interim mitigation

Update PHP Everywhere to version 2.0.4 or later. If immediate update is not possible, disable the plugin and review user roles with edit-post capabilities for suspicious activity.

Recommended fix Moderate confidence

Version 2.0.4 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'PHP Everywhere' in the plugin list
  4. Check if an update is available (if not, manually download version 2.0.4 or later from wordpress.org)
  5. Update the plugin to the latest available version
Caveat Minor plugin version updates typically have no breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Php Everywhere Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24664 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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