WP Beacon
Critical code_pattern
Resolved · benign_architectural_concern
2026-04-30 15:25:31 (2mo ago)
| Slug | a4-barcode-generator |
|---|---|
| Pattern | unserialize_after_remote_call |
| Kind | builtin |
| Version | 3.4.12 |
| Hit count | 1 |
| First hit |
|
| Explanation | a remote HTTP fetch (`wp_remote_*` / `curl_exec`) is followed by `@unserialize` within the same file — classic PHP Object Injection C2 gadget. The error-suppressed form is the tell: legit code wants to know when deserialize fails; attackers suppress so malformed gadgets do not leak. A real finding regardless of author intent: any plugin that deserializes remote responses without validation is a latent RCE chain if the remote endpoint is ever compromised. |
View raw JSON
{
"slug": "a4-barcode-generator",
"pattern": "unserialize_after_remote_call",
"kind": "builtin",
"version": "3.4.12",
"hit_count": 1,
"first_hit": {
"file": "class/Updater/WpAutoUpdate.php",
"line": 148,
"snippet": "L145: $request = wp_remote_post($this->update_path, $params); \u2192 L148: $serverData = @unserialize($request['body']);"
},
"explanation": "a remote HTTP fetch (`wp_remote_*` / `curl_exec`) is followed by `@unserialize` within the same file \u2014 classic PHP Object Injection C2 gadget. The error-suppressed form is the tell: legit code wants to know when deserialize fails; attackers suppress so malformed gadgets do not leak. A real finding regardless of author intent: any plugin that deserializes remote responses without validation is a latent RCE chain if the remote endpoint is ever compromised."
}