{"vulnerability": "CVE-2022-2466", "sightings": [{"uuid": "96da2efc-c36f-4d5b-8ee0-64a01dd76a4e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24663", "type": "seen", "source": "https://t.me/true_secator/2616", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 RCE \u0432 \u043f\u043b\u0430\u0433\u0438\u043d\u0435 PHP Everywhere \u0434\u043b\u044f WordPress, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0431\u043e\u043b\u0435\u0435 \u0447\u0435\u043c \u043d\u0430 30 000 \u0432\u0435\u0431-\u0441\u0430\u0439\u0442\u043e\u0432 \u043f\u043e \u0432\u0441\u0435\u043c\u0443 \u043c\u0438\u0440\u0443.\n\nPHP Everywhere - \u044d\u0442\u043e \u043f\u043b\u0430\u0433\u0438\u043d, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430\u043c WordPress \u0432\u0441\u0442\u0430\u0432\u043b\u044f\u0442\u044c \u043a\u043e\u0434 PHP \u043d\u0430 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u044b, \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f, \u0431\u043e\u043a\u043e\u0432\u0443\u044e \u043f\u0430\u043d\u0435\u043b\u044c \u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0439 \u0431\u043b\u043e\u043a Gutenberg \u0434\u043b\u044f \u043e\u0442\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u0438\u044f \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u043e\u0433\u043e \u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430.\n\n\u0422\u0440\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0430\u043d\u0430\u043b\u0438\u0442\u0438\u043a\u0430\u043c\u0438\u00a0Wordfence, \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 WordPress (\u043e\u0442 2.0.3 \u0438 \u043d\u0438\u0436\u0435) \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e\u0442 \u0441\u043e\u0431\u043e\u0439 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0435:\n\n- CVE-2022-24663: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u043b\u044e\u0431\u043e\u0439 \u043f\u043e\u0434\u043f\u0438\u0441\u0447\u0438\u043a, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043e\u0442\u043f\u0440\u0430\u0432\u0438\u0442\u044c \u0437\u0430\u043f\u0440\u043e\u0441 \u0441 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u043c shortcode \u043d\u0430 PHP Everywhere, \u0438 \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u044b\u0439 \u043a\u043e\u0434 PHP \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n- CVE-2022-24664: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438 \u0447\u0435\u0440\u0435\u0437 \u043c\u0435\u0442\u0430\u0431\u043e\u043a\u0441 \u043f\u043b\u0430\u0433\u0438\u043d\u0430, \u043f\u0443\u0442\u0435\u043c \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f, \u0434\u043e\u0431\u0430\u0432\u0438\u0432 \u043c\u0435\u0442\u0430\u0431\u043e\u043a\u0441 PHP-\u043a\u043e\u0434\u0430, \u0430 \u0437\u0430\u0442\u0435\u043c \u043f\u0440\u043e\u0441\u043c\u043e\u0442\u0440\u0435\u0432 \u0435\u0433\u043e (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n- CVE-2022-24665: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u0435\u0435 \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438, \u0443 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0435\u0441\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c edit_posts \u0438 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u0434\u043e\u0431\u0430\u0432\u043b\u044f\u0442\u044c \u0431\u043b\u043e\u043a\u0438 PHP Everywhere Gutenberg, \u0438 \u0441\u0432\u044f\u0437\u0430\u043d \u0441 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u043c \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e \u0432 \u0443\u044f\u0437\u0432\u0438\u043c\u044b\u0445 \u0432\u0435\u0440\u0441\u0438\u044f\u0445 \u043f\u043b\u0430\u0433\u0438\u043d\u0430 (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n\n\u0412 \u0442\u043e \u0432\u0440\u0435\u043c\u044f \u043a\u0430\u043a \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u0434\u0432\u0435 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0442\u0440\u0443\u0434\u043d\u043e \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u0442\u044c, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u043e\u043d\u0438 \u0442\u0440\u0435\u0431\u0443\u044e\u0442 \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0430, \u0430 \u043f\u0435\u0440\u0432\u0430\u044f \u0433\u043e\u0440\u0430\u0437\u0434\u043e \u0431\u043e\u043b\u0435\u0435 \u043e\u0442\u043a\u0440\u044b\u0442\u0430 \u0434\u043b\u044f \u0431\u043e\u043b\u0435\u0435 \u0448\u0438\u0440\u043e\u043a\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u0430 \u043f\u043e\u0434\u043f\u0438\u0441\u0447\u0438\u043a\u0443 \u043d\u0430 \u0441\u0430\u0439\u0442\u0435. \u0412\u043e \u0432\u0441\u0435\u0445 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u043e\u0433\u043e \u043a\u043e\u0434\u0430 \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 \u043c\u043e\u0436\u0435\u0442 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a \u0435\u0433\u043e \u043f\u043e\u043b\u043d\u043e\u043c\u0443 \u0437\u0430\u0445\u0432\u0430\u0442\u0443, \u0447\u0442\u043e \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043d\u0430\u0438\u0445\u0443\u0434\u0448\u0438\u043c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u044b\u043c \u0441\u0446\u0435\u043d\u0430\u0440\u0438\u0435\u043c \u0441 \u0442\u043e\u0447\u043a\u0438 \u0437\u0440\u0435\u043d\u0438\u044f \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438.\n\n\u041a\u043e\u043c\u0430\u043d\u0434\u0430 Wordfence \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0430 \u0438 \u043f\u0440\u043e\u0438\u043d\u0444\u043e\u0440\u043c\u0438\u0440\u043e\u0432\u0430\u043b\u0430 \u0430\u0432\u0442\u043e\u0440\u0430 PHP Everywhere \u043e\u0431 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 4 \u044f\u043d\u0432\u0430\u0440\u044f 2022 \u0433\u043e\u0434\u0430, \u0430 10 \u044f\u043d\u0432\u0430\u0440\u044f \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0432 \u0440\u0430\u043c\u043a\u0430\u0445 \u0432\u0435\u0440\u0441\u0438\u0438 3.0.0.\n\n\u0421\u043e\u0433\u043b\u0430\u0441\u043d\u043e\u00a0\u0441\u0442\u0430\u0442\u0438\u0441\u0442\u0438\u043a\u0435 \u0437\u0430\u0433\u0440\u0443\u0437\u043e\u043a\u00a0\u043d\u0430 WordPress, \u0442\u043e\u043b\u044c\u043a\u043e 15 000 \u0438\u0437 30 000 \u043e\u0431\u043d\u043e\u0432\u0438\u043b\u0438 \u043f\u043b\u0430\u0433\u0438\u043d \u0441 \u043c\u043e\u043c\u0435\u043d\u0442\u0430 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0448\u0438\u0431\u043e\u043a. \u0412 \u0432\u0438\u0434\u0443 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u043e\u0441\u0442\u0430\u0432\u0448\u0438\u043c\u0441\u044f \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c PHP Everywhere \u043d\u0430\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c\u0441\u044f \u0434\u043e \u0432\u0435\u0440\u0441\u0438\u0438 3.0.0.", "creation_timestamp": "2022-02-10T16:20:00.000000Z"}, {"uuid": "ca5751e5-a5ec-4369-9f38-03af58eb7013", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24665", "type": "seen", "source": "https://t.me/true_secator/2616", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 RCE \u0432 \u043f\u043b\u0430\u0433\u0438\u043d\u0435 PHP Everywhere \u0434\u043b\u044f WordPress, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0431\u043e\u043b\u0435\u0435 \u0447\u0435\u043c \u043d\u0430 30 000 \u0432\u0435\u0431-\u0441\u0430\u0439\u0442\u043e\u0432 \u043f\u043e \u0432\u0441\u0435\u043c\u0443 \u043c\u0438\u0440\u0443.\n\nPHP Everywhere - \u044d\u0442\u043e \u043f\u043b\u0430\u0433\u0438\u043d, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430\u043c WordPress \u0432\u0441\u0442\u0430\u0432\u043b\u044f\u0442\u044c \u043a\u043e\u0434 PHP \u043d\u0430 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u044b, \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f, \u0431\u043e\u043a\u043e\u0432\u0443\u044e \u043f\u0430\u043d\u0435\u043b\u044c \u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0439 \u0431\u043b\u043e\u043a Gutenberg \u0434\u043b\u044f \u043e\u0442\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u0438\u044f \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u043e\u0433\u043e \u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430.\n\n\u0422\u0440\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0430\u043d\u0430\u043b\u0438\u0442\u0438\u043a\u0430\u043c\u0438\u00a0Wordfence, \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 WordPress (\u043e\u0442 2.0.3 \u0438 \u043d\u0438\u0436\u0435) \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e\u0442 \u0441\u043e\u0431\u043e\u0439 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0435:\n\n- CVE-2022-24663: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u043b\u044e\u0431\u043e\u0439 \u043f\u043e\u0434\u043f\u0438\u0441\u0447\u0438\u043a, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043e\u0442\u043f\u0440\u0430\u0432\u0438\u0442\u044c \u0437\u0430\u043f\u0440\u043e\u0441 \u0441 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u043c shortcode \u043d\u0430 PHP Everywhere, \u0438 \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u044b\u0439 \u043a\u043e\u0434 PHP \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n- CVE-2022-24664: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438 \u0447\u0435\u0440\u0435\u0437 \u043c\u0435\u0442\u0430\u0431\u043e\u043a\u0441 \u043f\u043b\u0430\u0433\u0438\u043d\u0430, \u043f\u0443\u0442\u0435\u043c \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f, \u0434\u043e\u0431\u0430\u0432\u0438\u0432 \u043c\u0435\u0442\u0430\u0431\u043e\u043a\u0441 PHP-\u043a\u043e\u0434\u0430, \u0430 \u0437\u0430\u0442\u0435\u043c \u043f\u0440\u043e\u0441\u043c\u043e\u0442\u0440\u0435\u0432 \u0435\u0433\u043e (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n- CVE-2022-24665: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u0435\u0435 \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438, \u0443 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0435\u0441\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c edit_posts \u0438 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u0434\u043e\u0431\u0430\u0432\u043b\u044f\u0442\u044c \u0431\u043b\u043e\u043a\u0438 PHP Everywhere Gutenberg, \u0438 \u0441\u0432\u044f\u0437\u0430\u043d \u0441 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u043c \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e \u0432 \u0443\u044f\u0437\u0432\u0438\u043c\u044b\u0445 \u0432\u0435\u0440\u0441\u0438\u044f\u0445 \u043f\u043b\u0430\u0433\u0438\u043d\u0430 (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n\n\u0412 \u0442\u043e \u0432\u0440\u0435\u043c\u044f \u043a\u0430\u043a \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u0434\u0432\u0435 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0442\u0440\u0443\u0434\u043d\u043e \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u0442\u044c, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u043e\u043d\u0438 \u0442\u0440\u0435\u0431\u0443\u044e\u0442 \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0430, \u0430 \u043f\u0435\u0440\u0432\u0430\u044f \u0433\u043e\u0440\u0430\u0437\u0434\u043e \u0431\u043e\u043b\u0435\u0435 \u043e\u0442\u043a\u0440\u044b\u0442\u0430 \u0434\u043b\u044f \u0431\u043e\u043b\u0435\u0435 \u0448\u0438\u0440\u043e\u043a\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u0430 \u043f\u043e\u0434\u043f\u0438\u0441\u0447\u0438\u043a\u0443 \u043d\u0430 \u0441\u0430\u0439\u0442\u0435. \u0412\u043e \u0432\u0441\u0435\u0445 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u043e\u0433\u043e \u043a\u043e\u0434\u0430 \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 \u043c\u043e\u0436\u0435\u0442 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a \u0435\u0433\u043e \u043f\u043e\u043b\u043d\u043e\u043c\u0443 \u0437\u0430\u0445\u0432\u0430\u0442\u0443, \u0447\u0442\u043e \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043d\u0430\u0438\u0445\u0443\u0434\u0448\u0438\u043c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u044b\u043c \u0441\u0446\u0435\u043d\u0430\u0440\u0438\u0435\u043c \u0441 \u0442\u043e\u0447\u043a\u0438 \u0437\u0440\u0435\u043d\u0438\u044f \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438.\n\n\u041a\u043e\u043c\u0430\u043d\u0434\u0430 Wordfence \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0430 \u0438 \u043f\u0440\u043e\u0438\u043d\u0444\u043e\u0440\u043c\u0438\u0440\u043e\u0432\u0430\u043b\u0430 \u0430\u0432\u0442\u043e\u0440\u0430 PHP Everywhere \u043e\u0431 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 4 \u044f\u043d\u0432\u0430\u0440\u044f 2022 \u0433\u043e\u0434\u0430, \u0430 10 \u044f\u043d\u0432\u0430\u0440\u044f \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0432 \u0440\u0430\u043c\u043a\u0430\u0445 \u0432\u0435\u0440\u0441\u0438\u0438 3.0.0.\n\n\u0421\u043e\u0433\u043b\u0430\u0441\u043d\u043e\u00a0\u0441\u0442\u0430\u0442\u0438\u0441\u0442\u0438\u043a\u0435 \u0437\u0430\u0433\u0440\u0443\u0437\u043e\u043a\u00a0\u043d\u0430 WordPress, \u0442\u043e\u043b\u044c\u043a\u043e 15 000 \u0438\u0437 30 000 \u043e\u0431\u043d\u043e\u0432\u0438\u043b\u0438 \u043f\u043b\u0430\u0433\u0438\u043d \u0441 \u043c\u043e\u043c\u0435\u043d\u0442\u0430 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0448\u0438\u0431\u043e\u043a. \u0412 \u0432\u0438\u0434\u0443 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u043e\u0441\u0442\u0430\u0432\u0448\u0438\u043c\u0441\u044f \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c PHP Everywhere \u043d\u0430\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c\u0441\u044f \u0434\u043e \u0432\u0435\u0440\u0441\u0438\u0438 3.0.0.", "creation_timestamp": "2022-02-10T16:20:00.000000Z"}, {"uuid": "7af612d0-592c-41f6-9db3-795b80b79e67", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24664", "type": "seen", "source": "https://t.me/true_secator/2616", "content": "\u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 RCE \u0432 \u043f\u043b\u0430\u0433\u0438\u043d\u0435 PHP Everywhere \u0434\u043b\u044f WordPress, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0431\u043e\u043b\u0435\u0435 \u0447\u0435\u043c \u043d\u0430 30 000 \u0432\u0435\u0431-\u0441\u0430\u0439\u0442\u043e\u0432 \u043f\u043e \u0432\u0441\u0435\u043c\u0443 \u043c\u0438\u0440\u0443.\n\nPHP Everywhere - \u044d\u0442\u043e \u043f\u043b\u0430\u0433\u0438\u043d, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430\u043c WordPress \u0432\u0441\u0442\u0430\u0432\u043b\u044f\u0442\u044c \u043a\u043e\u0434 PHP \u043d\u0430 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u044b, \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f, \u0431\u043e\u043a\u043e\u0432\u0443\u044e \u043f\u0430\u043d\u0435\u043b\u044c \u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0439 \u0431\u043b\u043e\u043a Gutenberg \u0434\u043b\u044f \u043e\u0442\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u0438\u044f \u0434\u0438\u043d\u0430\u043c\u0438\u0447\u0435\u0441\u043a\u043e\u0433\u043e \u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430.\n\n\u0422\u0440\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0431\u044b\u043b\u0438 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u044b \u0430\u043d\u0430\u043b\u0438\u0442\u0438\u043a\u0430\u043c\u0438\u00a0Wordfence, \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u044e\u0442 \u0432\u0441\u0435 \u0432\u0435\u0440\u0441\u0438\u0438 WordPress (\u043e\u0442 2.0.3 \u0438 \u043d\u0438\u0436\u0435) \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u044e\u0442 \u0441\u043e\u0431\u043e\u0439 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0435:\n\n- CVE-2022-24663: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u043b\u044e\u0431\u043e\u0439 \u043f\u043e\u0434\u043f\u0438\u0441\u0447\u0438\u043a, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043e\u0442\u043f\u0440\u0430\u0432\u0438\u0442\u044c \u0437\u0430\u043f\u0440\u043e\u0441 \u0441 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u043c shortcode \u043d\u0430 PHP Everywhere, \u0438 \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u044b\u0439 \u043a\u043e\u0434 PHP \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n- CVE-2022-24664: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438 \u0447\u0435\u0440\u0435\u0437 \u043c\u0435\u0442\u0430\u0431\u043e\u043a\u0441 \u043f\u043b\u0430\u0433\u0438\u043d\u0430, \u043f\u0443\u0442\u0435\u043c \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f \u0441\u043e\u043e\u0431\u0449\u0435\u043d\u0438\u044f, \u0434\u043e\u0431\u0430\u0432\u0438\u0432 \u043c\u0435\u0442\u0430\u0431\u043e\u043a\u0441 PHP-\u043a\u043e\u0434\u0430, \u0430 \u0437\u0430\u0442\u0435\u043c \u043f\u0440\u043e\u0441\u043c\u043e\u0442\u0440\u0435\u0432 \u0435\u0433\u043e (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n- CVE-2022-24665: \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c RCE, \u0435\u0435 \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438, \u0443 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0435\u0441\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c edit_posts \u0438 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u0434\u043e\u0431\u0430\u0432\u043b\u044f\u0442\u044c \u0431\u043b\u043e\u043a\u0438 PHP Everywhere Gutenberg, \u0438 \u0441\u0432\u044f\u0437\u0430\u043d \u0441 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u043c \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e \u0432 \u0443\u044f\u0437\u0432\u0438\u043c\u044b\u0445 \u0432\u0435\u0440\u0441\u0438\u044f\u0445 \u043f\u043b\u0430\u0433\u0438\u043d\u0430 (\u043e\u0446\u0435\u043d\u043a\u0430 CVSS v3: 9,9).\n\n\u0412 \u0442\u043e \u0432\u0440\u0435\u043c\u044f \u043a\u0430\u043a \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u0434\u0432\u0435 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0442\u0440\u0443\u0434\u043d\u043e \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u0442\u044c, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u043e\u043d\u0438 \u0442\u0440\u0435\u0431\u0443\u044e\u0442 \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0430, \u0430 \u043f\u0435\u0440\u0432\u0430\u044f \u0433\u043e\u0440\u0430\u0437\u0434\u043e \u0431\u043e\u043b\u0435\u0435 \u043e\u0442\u043a\u0440\u044b\u0442\u0430 \u0434\u043b\u044f \u0431\u043e\u043b\u0435\u0435 \u0448\u0438\u0440\u043e\u043a\u043e\u0439 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438, \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u0430 \u043f\u043e\u0434\u043f\u0438\u0441\u0447\u0438\u043a\u0443 \u043d\u0430 \u0441\u0430\u0439\u0442\u0435. \u0412\u043e \u0432\u0441\u0435\u0445 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u043e\u0433\u043e \u043a\u043e\u0434\u0430 \u043d\u0430 \u0441\u0430\u0439\u0442\u0435 \u043c\u043e\u0436\u0435\u0442 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a \u0435\u0433\u043e \u043f\u043e\u043b\u043d\u043e\u043c\u0443 \u0437\u0430\u0445\u0432\u0430\u0442\u0443, \u0447\u0442\u043e \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043d\u0430\u0438\u0445\u0443\u0434\u0448\u0438\u043c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u044b\u043c \u0441\u0446\u0435\u043d\u0430\u0440\u0438\u0435\u043c \u0441 \u0442\u043e\u0447\u043a\u0438 \u0437\u0440\u0435\u043d\u0438\u044f \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438.\n\n\u041a\u043e\u043c\u0430\u043d\u0434\u0430 Wordfence \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0430 \u0438 \u043f\u0440\u043e\u0438\u043d\u0444\u043e\u0440\u043c\u0438\u0440\u043e\u0432\u0430\u043b\u0430 \u0430\u0432\u0442\u043e\u0440\u0430 PHP Everywhere \u043e\u0431 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 4 \u044f\u043d\u0432\u0430\u0440\u044f 2022 \u0433\u043e\u0434\u0430, \u0430 10 \u044f\u043d\u0432\u0430\u0440\u044f \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0432 \u0440\u0430\u043c\u043a\u0430\u0445 \u0432\u0435\u0440\u0441\u0438\u0438 3.0.0.\n\n\u0421\u043e\u0433\u043b\u0430\u0441\u043d\u043e\u00a0\u0441\u0442\u0430\u0442\u0438\u0441\u0442\u0438\u043a\u0435 \u0437\u0430\u0433\u0440\u0443\u0437\u043e\u043a\u00a0\u043d\u0430 WordPress, \u0442\u043e\u043b\u044c\u043a\u043e 15 000 \u0438\u0437 30 000 \u043e\u0431\u043d\u043e\u0432\u0438\u043b\u0438 \u043f\u043b\u0430\u0433\u0438\u043d \u0441 \u043c\u043e\u043c\u0435\u043d\u0442\u0430 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043e\u0448\u0438\u0431\u043e\u043a. \u0412 \u0432\u0438\u0434\u0443 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u043e\u0441\u0442\u0430\u0432\u0448\u0438\u043c\u0441\u044f \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044f\u043c PHP Everywhere \u043d\u0430\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u043c \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c\u0441\u044f \u0434\u043e \u0432\u0435\u0440\u0441\u0438\u0438 3.0.0.", "creation_timestamp": "2022-02-10T16:20:00.000000Z"}, {"uuid": "f3a59c97-ccc1-46f1-b415-d32381fc710f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24669", "type": "seen", "source": "https://t.me/cibsecurity/52168", "content": "\u203c CVE-2022-24669 \u203c\n\nIt may be possible to gain some details of the deployment through a well-crafted attack. This may allow that data to be used to probe internal network services.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-10-27T20:33:38.000000Z"}, {"uuid": "ef1d72cd-1dc1-4786-a83b-85a1026f15a9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24660", "type": "seen", "source": "https://t.me/cibsecurity/46640", "content": "\u203c CVE-2022-24660 \u203c\n\nThe debug interface of Goldshell ASIC Miners v2.2.1 and below was discovered to be exposed publicly on the web interface, allowing attackers to access passwords and other sensitive information in plaintext.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-07-20T16:19:58.000000Z"}, {"uuid": "cddabc48-276b-491e-a709-5d9d3b05141f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24663", "type": "seen", "source": "https://t.me/cibsecurity/37600", "content": "\u203c CVE-2022-24663 \u203c\n\nPHP Everywhere <= 2.0.3 included functionality that allowed execution of PHP Code Snippets via WordPress shortcodes, which can be used by any authenticated user.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-02-16T20:42:08.000000Z"}, {"uuid": "c364ee01-9527-4427-9831-206311261dab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24668", "type": "seen", "source": "https://t.me/cibsecurity/37167", "content": "\u203c CVE-2022-24668 \u203c\n\nA program using swift-nio-http2 is vulnerable to a denial of service attack caused by a network peer sending ALTSVC or ORIGIN frames. This attack affects all swift-nio-http2 versions from 1.0.0 to 1.19.1. This vulnerability is caused by a logical error after frame parsing but before frame handling. ORIGIN and ALTSVC frames are not currently supported by swift-nio-http2, and should be ignored. However, one code path that encounters them has a deliberate trap instead. This was left behind from the original development process and was never removed. Sending an ALTSVC or ORIGIN frame does not require any special permission, so any HTTP/2 connection peer may send such a frame. For clients, this means any server to which they connect may launch this attack. For servers, anyone they allow to connect to them may launch such an attack. The attack is low-effort: it takes very little resources to send one of these frames. The impact on availability is high: receiving the frame immediately crashes the server, dropping all in-flight connections and causing the service to need to restart. It is straightforward for an attacker to repeatedly send these frames, so attackers require very few resources to achieve a substantial denial of service. The attack does not have any confidentiality or integrity risks in and of itself. This is a controlled, intentional crash. However, sudden process crashes can lead to violations of invariants in services, so it is possible that this attack can be used to trigger an error condition that has confidentiality or integrity risks. The risk can be mitigated if untrusted peers can be prevented from communicating with the service. This mitigation is not available to many services. The issue is fixed by rewriting the parsing code to correctly handle the condition. The issue was found by automated fuzzing by oss-fuzz.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-02-10T02:19:29.000000Z"}, {"uuid": "d2f4b512-b107-458b-8aae-4f3eefe2e743", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-2466", "type": "published-proof-of-concept", "source": "https://t.me/CVEhub/227", "content": "\ud83d\udc7eCVE SERVICE \ud83c\udff7#CVE\nMumber: CVE-2022-2466\nGithub: https://github.com/yuxblank/CVE-2022-2466---Request-Context-not-terminated-with-GraphQL\nDescribe: \n**", "creation_timestamp": "2026-07-18T18:00:04.203001Z"}, {"uuid": "43aabe63-d98d-4838-a88d-27278cc08349", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-2466", "type": "published-proof-of-concept", "source": "https://t.me/CVEhub/227", "content": "\ud83d\udc7eCVE SERVICE \ud83c\udff7#CVE\nMumber: CVE-2022-2466\nGithub: https://github.com/yuxblank/CVE-2022-2466---Request-Context-not-terminated-with-GraphQL\nDescribe: \n**", "creation_timestamp": "2026-07-19T00:00:10.700060Z"}, {"uuid": "c29a692c-f7e9-4213-aecb-d009f4034be0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24663", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-01T20:01:56.264523Z"}, {"uuid": "cd3b36c2-f1b4-4c42-898c-e48097be601a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24665", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-01T20:01:56.330668Z"}, {"uuid": "12dc27e0-2603-4986-b597-67d3e38e54f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24664", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-01T20:01:56.367526Z"}, {"uuid": "8878cb73-e5fa-49c5-b254-f494acd0a78b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24663", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-02T01:02:16.178804Z"}, {"uuid": "5dd4c964-8575-4db8-8524-5bfb6d87ec1a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24664", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-02T01:02:16.621407Z"}, {"uuid": "9f8e7c8f-baa0-4660-ae87-4b1a94536b11", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24665", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-02T01:02:16.569914Z"}, {"uuid": "de3ffe09-8fc5-4c61-8116-e3ca055815a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24665", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-06T10:00:07.501226Z"}, {"uuid": "a98049d2-e5da-4a47-8a94-a905891a0fe7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24664", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-06T10:00:07.548657Z"}, {"uuid": "139496a4-27c1-4b51-bd76-6f128a3ed3fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24663", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-06T10:00:07.595505Z"}, {"uuid": "d98fdb93-dcd1-4d09-bfe5-d5f5d613e015", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24665", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-07T01:00:24.299562Z"}, {"uuid": "5c737661-9b4f-4870-a6ed-97472554d8f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24664", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-07T01:00:24.333218Z"}, {"uuid": "50083da2-fdf5-4702-8080-4846cac78920", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-24663", "type": "seen", "source": "https://t.me/hacking_Attack/42319", "content": "Black Hat Ethical Hacking\nPHP Everywhere RCE flaws threaten thousands of WordPress sites\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png PHP Everywhere RCE flaws threaten thousands of WordPress sitesPost Views: 176 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nResearchers found three critical remote code execution (RCE) vulnerabilities in the \u2018PHP Everywhere\u2019 plugin for WordPress, used by over 30,000 websites worldwide.\nPHP Everywhere is a plugin that allows WordPress admins to insert PHP code in pages, posts, the sidebar, or any Gutenberg block, and use it to display dynamic content based on evaluated PHP expressions. Three RCE flawsThe three vulnerabilities were discovered by security analysts at Wordfence\u00a0and can be exploited by contributors or subscribers, affecting all WordPress versions from 2.0.3 and below.\n\nHere\u2019s a short description of the flaws:\n\n* CVE-2022-24663\u00a0\u2013 Remote code execution flaw exploitable by any subscriber\u00a0 by allowing them to send a request with the \u2018shortcode\u2019 parameter set to PHP Everywhere, and execute arbitrary PHP code on the site. (CVSS v3 score: 9.9)\n* CVE-2022-24664\u00a0\u2013 RCE vulnerability exploitable by contributors via the plugin\u2019s metabox. An attacker would create a post, add a PHP code metabox, and then preview it. (CVSS v3 score: 9.9)\n* CVE-2022-24665\u00a0\u2013 RCE flaw exploitable by contributors who have the \u2018edit_posts\u2019 capability and can add PHP Everywhere Gutenberg blocks. Default security setting on vulnerable plugin versions isn\u2019t on \u2018admin-only\u2019 as it should be. (CVSS v3 score: 9.9)\n\nWhile the last two flaws aren\u2019t easily exploitable as they require contributor-level permissions, the first vulnerability is a lot more open to broader exploitation as it can be exploited by just being a subscriber on the site.\n\nFor example, a logged-in customer on a site is considered a \u2018subscriber,\u2019\u00a0so merely registering on the target platform would be enough to gain enough privileges for malicious PHP code execution.\n\nIn all cases, executing arbitrary code on a site can lead to a complete site takeover, which is the worst possible scenario in website security.\nSee Also: Complete Offensive Security and Ethical Hacking Course Fix only for Block editorWordfence\u2019s team discovered the vulnerabilities on January 4, 2022, and informed the author of PHP Everywhere of its findings.\n\nThe vendor released a security update on January 10, 2022, with version 3.0.0, which took a major version number bump because it required a substantial code rewrite.\n\nWhile the developers fixed the update last month, it is not uncommon for admins to not regularly update their WordPress site and plugins. According to the download stats\u00a0on WordPress.org, only 15,000 installs out of 30,000 have updated the plugin since the bugs were fixed.\nSee Also: Windows vulnerability with new public exploits lets you become admin Therefore, due to the severity of these vulnerabilities, all users of PHP Everywhere are strongly advised to make sure they have upgraded to PHP Everywhere version 3.0.0, which is the latest available at this time.\n\nNote that if you\u2019re using the Classic Editor on your site, you will need to uninstall the plugin and find another solution for hosting custom PHP code on its components.\n\nThat is because version 3.0.0 only supports PHP snippets via the Block editor, and it\u2019s unlikely that the author will work on restoring functionality for the sun-setting Classic.\nSee Also: Offensive Security Tool: Stratus Red Team\nAre u a security researcher? Or a company that writes articles or write ups about Cyber Security, O[...]", "creation_timestamp": "2026-09-07T01:00:24.368212Z"}]}