Profile Builder Pro <= 3.14.5 - Unauthenticated PHP Object Injection
Strategic Overview
- Status
- Patched in 3.14.6
- Affected Plugin
- Profile Builder Pro
- Affected Version
<= 3.14.5- CVSS
- 8.1High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-7647
At a glance
CVE-2026-7647 is a high-severity Deserialization of Untrusted Data vulnerability in the Profile Builder Pro WordPress plugin, affecting versions <= 3.14.5. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.14.6; sites on affected versions should update now. Disclosed May 2026, reported by 0xbro.
Vulnerability Overview
The Profile Builder Pro plugin for WordPress is vulnerable to PHP Object Injection in all versions up to and including 3.14.5. This is due to the use of PHP's maybe_unserialize() function on the attacker-controlled 'args' POST parameter within the wppb_request_users_pins_action_callback() AJAX handler, which lacked any nonce verification, type checking, or input validation before deserialization. Because the handler was registered with both wp_ajax_ and wp_ajax_nopriv_ hooks, it was reachable by completely unauthenticated users. This makes it possible for unauthenticated attackers to inject arbitrary PHP objects into application memory.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Profile Builder Pro <= 3.14.5 carries this weakness at args, and reaching it takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Profile Builder Pro the fix is 3.14.6: builds <= 3.14.5 are affected, anything from 3.14.6 onward is not.
Remediation
Update to version 3.14.6, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Profile Builder Pro 3.14.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in Profile Builder Pro
- 9.8Profile Builder <= 3.1.0 Privilege Escalation
- 8.8CVE-2024-22140: Profile Builder Pro <= 3.10.0 CSRF
CVE-2024-22140 - 8.8Profile Builder/Profile Builder Pro <= 3.3.2 Blind SQL Injection
- 7.5CVE-2026-27413: Profile Builder Pro < 3.14.0 SQL Injection
CVE-2026-27413 - 7.2CVE-2026-42385: Profile Builder Pro <= 3.15.0 Stored XSS
CVE-2026-42385 - 6.5CVE-2024-22141: Profile Builder Pro Time-Based One-Time Password Info
CVE-2024-22141 - 6.1CVE-2024-22142: Profile Builder Pro <= 3.10.0 Reflected XSS
CVE-2024-22142
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C