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": "wpheka-web-server-information",
"pattern": "unserialize_after_remote_call",
"kind": "builtin",
"version": "1.7",
"hit_count": 1,
"first_hit": {
"file": "includes/class-wpheka-info-admin-webserver.php",
"line": 109,
"snippet": "L109: $query = @unserialize( wp_remote_retrieve_body( wp_remote_get( 'http://ip-api.com/php \u2192 L109: $query = @unserialize( wp_remote_retrieve_body( wp_remote_get( 'http://ip-api.com/php"
},
"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."
}
SVN committers (2)
Accounts with actual commit access to wpheka-web-server-information on plugins.svn.wordpress.org, reconstructed from svn log. This is the list that matters for ownership changes — not the readme contributors.
Names the plugin's readme declares as contributors. A soft signal — anyone can be listed. The SVN access column is the ground-truth cross-reference: does this contributor actually commit code?
WP Beacon