PHP Object Injection in Pimcore Newsletter getObjectByToken
The getObjectByToken function in Newsletter.php within the Pimcore_Tool_Newsletter module (versions 1.4.9 through 2.0.0) is vulnerable to PHP object injection. The vulnerability arises from improper handling of objects obtained by unserializing Lucene search data, allowing remote attackers to inject arbitrary PHP objects. Specifically, exploitation can occur via a crafted Zend_Pdf_ElementFactory_Proxy object and a pathname containing a trailing null byte (\0), leading to arbitrary code execution.
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 remote attackers to execute arbitrary PHP code on the server, potentially leading to full compromise of the affected system. Attackers can leverage this to gain unauthorized access, escalate privileges, or further pivot within the environment.
If you can’t patch tonight, do this now.
Restrict access to the vulnerable functionality to trusted users only. Employ web application firewalls (WAFs) to detect and block malicious payloads targeting unserialize operations. Monitor for suspicious activity and review code for unsafe use of unserialize.
Patch, then assume compromise.
Upgrade Pimcore to a version later than 2.0.0 where this vulnerability is patched. Ensure that all unserialize operations are performed on trusted data only, and consider using safer serialization mechanisms or input validation to prevent object injection.
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.