<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>BuddyPress (&lt;= 14.5.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/buddypress--14.5.0/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 30 Jul 2026 07:19:57 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/buddypress--14.5.0/feed.xml" rel="self" type="application/rss+xml"/><item><title>BuddyPress Insecure Deserialization Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-07-buddypress-deserialization/</link><pubDate>Thu, 30 Jul 2026 07:19:57 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-buddypress-deserialization/</guid><description>An insecure deserialization vulnerability in the BuddyPress WordPress plugin allows authenticated attackers to inject arbitrary PHP objects, potentially leading to remote code execution.</description><content:encoded><![CDATA[<p>The BuddyPress plugin for WordPress is vulnerable to an insecure deserialization flaw affecting all versions up to and including 14.5.0. The vulnerability resides in the <code>bp_unserialize_profile_field()</code> function, which invokes the native PHP <code>@unserialize()</code> function on XProfile textbox field data without specifying the <code>allowed_classes</code> parameter. Because the function processes user-controlled input, authenticated attackers with subscriber-level permissions or higher can inject malicious serialized PHP objects. If the target WordPress environment contains a suitable Property-Oriented Programming (POP) chain within its core, theme, or other installed plugins, this vulnerability can be leveraged to achieve remote code execution (RCE). The impact is significant due to the broad use of BuddyPress, and defenders should prioritize patching or restricting access to profile modification endpoints.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to the target WordPress site as a subscriber or user with profile modification permissions.</li>
<li>Attacker navigates to the XProfile field management or user profile settings interface.</li>
<li>Attacker crafts a malicious serialized PHP object designed to trigger a POP chain within the WordPress application environment.</li>
<li>Attacker submits the crafted payload via a textbox field POST request targeting the BuddyPress profile update endpoint.</li>
<li>The <code>bp_unserialize_profile_field()</code> function receives the malicious payload.</li>
<li>The application performs insecure deserialization of the injected object using <code>@unserialize()</code>.</li>
<li>The instantiated object triggers the POP chain during its lifecycle, resulting in unauthorized code execution.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The vulnerability poses a high risk to WordPress installations utilizing the BuddyPress plugin. Successful exploitation by an authenticated attacker can result in full site compromise, arbitrary command execution on the underlying server, and potential data exfiltration or site defacement. Given that the attack requires only basic subscriber access, the pool of potential attackers is large in multi-user environments.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the BuddyPress plugin to a version later than 14.5.0 immediately to mitigate CVE-2026-1360.</li>
<li>Audit WordPress environments for POP chain gadgets, particularly within custom plugins and themes, to understand the potential for secondary exploitation.</li>
<li>Monitor web server logs for suspicious POST requests to BuddyPress profile update endpoints that contain PHP serialized data patterns (e.g., <code>O:[0-9]+:</code>) in the input parameters.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>wordpress</category><category>deserialization</category><category>rce</category><category>web-vulnerability</category></item></channel></rss>