Remote Code Execution by by Contributor+ users via WordPress metabox

published 2022-02-16 4y ago modified 2026-06-17 4mo ago also EUVD-2022-29539

cvss: 9.9; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.7%; EPSS 1.7% chance of exploitation in 30 days, percentile 76%
public exploits: 0; none known

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.

Is CVE-2022-24664 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: last yr. (2025-01-31)

Exploit prediction

1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.9	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:N/I:P/A:N

Affected products

Alexander Fuchs PHP Everywhere

Classification

Weakness

CWE-94 Improper Control of Generation of Code

Technology feeds

WordPress rss critical rss

References

wordfence.com /blog/2022/02/critical-vulnerabilities-in-php-everywhere-allow-remote-code-execution/
third-party-advisory

Sources

CVE List CVE-2022-24664
NVD CVE-2022-24664

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.