CVE-2026-7647
Deferred Deferred - Pending Action
PHP Object Injection in Profile Builder Pro WordPress Plugin

Publication date: 2026-05-02

Last updated on: 2026-05-05

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-02
Last Modified
2026-05-05
Generated
2026-05-07
AI Q&A
2026-05-02
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wpbr profile_builder_pro to 3.14.5 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Profile Builder Pro plugin for WordPress has a vulnerability known as PHP Object Injection in all versions up to and including 3.14.5. This occurs because the plugin uses PHP's maybe_unserialize() function on the 'args' POST parameter without verifying the source or validating the input. The AJAX handler that processes this parameter does not check for a security nonce, type, or input validity before deserialization.

Since the handler is registered with both authenticated and unauthenticated AJAX hooks (wp_ajax_ and wp_ajax_nopriv_), attackers who are not logged in can exploit this to inject arbitrary PHP objects into the application's memory.


How can this vulnerability impact me? :

This vulnerability can have severe impacts because it allows unauthenticated attackers to inject arbitrary PHP objects into the application memory. This can lead to remote code execution or other malicious actions that compromise the confidentiality, integrity, and availability of the affected system.

  • Confidentiality: Attackers may access sensitive data.
  • Integrity: Attackers can modify or corrupt data.
  • Availability: Attackers can disrupt or disable the service.

What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should immediately update the Profile Builder Pro plugin for WordPress to a version later than 3.14.5 where the issue is fixed.

Additionally, consider disabling or restricting access to the AJAX handler wppb_request_users_pins_action_callback() to prevent unauthenticated users from reaching it.

Implementing nonce verification, input validation, and type checking on the 'args' POST parameter can also help prevent exploitation.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows unauthenticated attackers to inject arbitrary PHP objects into application memory, potentially leading to full compromise of confidentiality, integrity, and availability of affected systems.

Such a compromise could result in unauthorized access to sensitive personal data or protected health information, which would negatively impact compliance with standards and regulations like GDPR and HIPAA that require protection of such data.

Therefore, organizations using the affected Profile Builder Pro plugin versions may face increased risk of non-compliance due to potential data breaches or unauthorized data manipulation stemming from this vulnerability.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves the Profile Builder Pro WordPress plugin processing an attacker-controlled 'args' POST parameter via the wppb_request_users_pins_action_callback() AJAX handler without proper validation or nonce verification.

To detect exploitation attempts on your system or network, you can monitor HTTP POST requests targeting the AJAX endpoint that triggers the vulnerable handler. Specifically, look for POST requests to URLs containing 'admin-ajax.php' with the action parameter set to 'wppb_request_users_pins_action' and containing suspicious serialized PHP objects in the 'args' parameter.

Example command using curl to test if the endpoint is reachable (replace example.com with your domain):

  • curl -X POST -d "action=wppb_request_users_pins_action&args=O:1:\"A\":0:{}" https://example.com/wp-admin/admin-ajax.php -v

For network detection, you can use tools like tcpdump or Wireshark to filter HTTP POST requests to 'admin-ajax.php' with the specific action parameter. For example, using tcpdump:

  • tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'wppb_request_users_pins_action'

Additionally, reviewing web server logs for POST requests containing 'action=wppb_request_users_pins_action' and suspicious serialized data in the 'args' parameter can help identify attempts.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart