Code Injection in IPS Community Suite content.php
Invision Power Services IPS Community Suite, also known as Invision Power Board or IPB, before version 4.1.13 contains a code-injection vulnerability in applications/core/modules/front/system/content.php. When deployed with PHP before 5.4.24 or PHP 5.5.x before 5.5.8, an unauthenticated remote attacker can supply a crafted content_class parameter to execute arbitrary code.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a remote attacker to execute arbitrary code in the context of the affected IPS Community Suite application.
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, restrict access to the vulnerable content.php endpoint, apply web application firewall (WAF) rules to block malicious content_class parameter values, and ensure that only trusted users can access the affected functionality.
Patch, then assume compromise.
Upgrade IPS Community Suite to version 4.1.13 or later. Ensure the PHP runtime is updated to at least PHP 5.4.24 or a PHP 5.5 release at or after 5.5.8.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.