Php EverywhereWordPress extension · Php Everywhere Project
CVE-2022-24663
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 · uneditedPHP Everywhere <= 2.0.3 included functionality that allowed execution of PHP Code Snippets via WordPress shortcodes, which can be used by any authenticated user.
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 confidenceThe PHP Everywhere WordPress plugin versions 2.0.3 and below contains a critical access control flaw where the PHP code snippet execution functionality via shortcodes is exposed to all authenticated users, including low-privilege users like subscribers. This allows any logged-in user to execute arbitrary PHP code on the server, leading to full site compromise.
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.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if PHP Everywhere plugin is installedNavigate to WordPress admin > Plugins or inspect the /wp-content/plugins/php-everywhere/ directory via file manager/FTPAffected if The plugin directory exists and contains plugin files
-
Determine the installed versionCheck the plugin version in WordPress admin > Plugins > PHP Everywhere, or read the version header from the main plugin file (php-everywhere.php)Affected if The version listed is 2.0.3 or lower
-
Verify shortcode functionality is activeCheck if the [php_everywhere] shortcode is being processed by creating a test post/page with the shortcode and attempting to access it as a low-privilege user, or inspect plugin settings for shortcode execution statusAffected if The shortcode is registered and functional on the site
-
Confirm low-privilege user accessLog in as a subscriber-level user and attempt to access a page containing the [php_everywhere] shortcode, or inspect user role capabilities to see if non-admin users can trigger PHP executionAffected if A subscriber or other low-privilege user can trigger PHP code execution via the shortcode
If PHP Everywhere version 2.0.3 or lower is installed AND the shortcode functionality is active AND low-privilege users can access it, the environment is vulnerable to CVE-2022-24663.
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.
dbcve · scopedUpdate PHP Everywhere to the latest version immediately. If patching is not possible, disable the plugin or implement additional access controls at the server level to prevent unauthorized PHP execution.
PHP Everywhere 2.0.4 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'PHP Everywhere' in the plugin list
- Click 'Update Now' if an update is available, or manually upload version 2.0.4 or later of the plugin
- Verify the update was successfully applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Php Everywhere
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24663 — 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-2022-24663 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