Supply Chain Attack affecting post-grid-pro and possibly other plugins

Ticket for: Post Grid
0
Supply Chain Attack affecting post-grid-pro and possibly other plugins 1
Mike Gozdiskowski
Nov 14, 2026 08:00 PM 0 Answers
Member Since Jan 1970
Unsolved Solved Mark as Solved Mark as Unsolved
Subscribed Subscribe Not subscribe
Flag(0)

We are seeing a backdoor in the 3.3.26 version of post-grid-pro after sites update from your official source.

Affected file

  • post-grid-pro/includes/class-post-grid-license.php, class class_post_grid_license2
  • Plugin header and post_grid_pro_version: 3.3.26
  • readme.txt changelog stops at 3.3.22

 

What the code does

The injected block appears three times: once in __construct() and twice in check_plugin_update(), which is hooked to init. It runs on every front-end and admin request, with no login or capability check.

  1. Reads attacker input from any of three places, in this order:
    • HTTP header X-Console-State ($_SERVER['HTTP_X_CONSOLE_STATE'])
    • cookie wp_console_state
    • POST field post_grid_console_state
  2. Decodes it with unserialize(hex2bin(...)). Passing untrusted input to unserialize() is a PHP object-injection risk even before the next steps.
  3. Checks a password. The resulting object must have key and content properties, and sha256(key) must equal
    e28c46a65d7daf47285049dc9469f88c77f315857c0590a6d5d12b7ec39097e7.
    Only someone who knows that key can use the backdoor.
  4. Runs arbitrary PHP. It strips a leading <?php from content, then writes '<?php ' . content to a temp file. It tries sys_get_temp_dir() first, then wp-content/uploads/, then the plugin’s includes/ folder, with the filename prefix co. It then includes the file.
  5. Removes the evidence. It deletes the temp file right after execution.
  6. Returns the output. It captures the output, clears all output buffers, and sends it to the requester as text/plain with a 200 status, then calls exit.
  7. Leaves markers and blocks updates. It stores the last output in the option post_grid_console_last and sets post_grid_console_frozen = 1. check_plugin_update() skips creating WP_AutoUpdate when that flag is set, so once the backdoor has been used, the site stops receiving Post Grid Pro updates, including any fixed release.
0 Subscribers
Submit Answer
Please login to submit answer.
0 Answers
Sort By: