Unsafe Deserialization in BuddyPress (WordPress plugin) (CVE-2026-1360)
Summary
Vulnerability in BuddyPress (WordPress plugin) (CVE-2026-1360). Successful exploitation can lead to full system takeover. Exploitable via allowed_classes.
Original description
The description as published by the source.
The BuddyPress plugin for WordPress is vulnerable to Deserialization of Untrusted Data in all versions up to, and including, 14.5.0 This is due to the bp_unserialize_profile_field() function using @unserialize() without the allowed_classes parameter on user-controlled XProfile field data. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary PHP objects via XProfile textbox fields, which could lead to remote code execution if a suitable POP chain is available in the WordPress environment.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-1360 has been found in BuddyPress (WordPress plugin).
Attackers can target a specific entry point like allowed_classes over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "BuddyPress (WordPress plugin) CVE-2026-1360" on the vendor's site.
CVE-2026-1360 (BuddyPress (WordPress plugin)) — CWE-502 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: allowed_classes
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in BuddyPress (WordPress plugin). Attackers reach the vulnerable code path via allowed_classes.
Check the vendor advisory for the affected versions of BuddyPress (WordPress plugin). Attack surface: allowed_classes.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで BuddyPress (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。