dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-7647

HIGH · 8.1 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Profile Builder Pro WordPress plugin (versions up to 3.14.5) contains a PHP Object Injection vulnerability in the wppb_request_users_pins_action_callback() AJAX handler. The handler uses maybe_unserialize() on the attacker-controlled 'args' POST parameter without any nonce verification, type checking, or input validation. Since the handler is registered with both wp_ajax_ and wp_ajax_nopriv_ hooks, it is accessible to completely unauthenticated users, allowing injection of arbitrary PHP objects.

MitigationUpdate to a patched version of Profile Builder Pro as soon as available. As a temporary measure, disable the plugin or deploy WAF rules to block the affected AJAX endpoint until a patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Profile Builder Pro is installed
    Check the WordPress plugins directory or use WP-CLI: wp plugin list --name='profile-builder-pro'
    Affected if The plugin is not installed or is the free version only
  2. Check the installed version
    Inspect the plugin main file header or run: wp plugin list --name='profile-builder-pro' --format=json
    Affected if Version is 3.14.5 or lower (any version up to 3.14.5 is affected)
  3. Confirm the vulnerable AJAX handler exists
    Search the plugin files for 'wppb_request_users_pins_action_callback' function definition, typically in AJAX-related files
    Affected if The function exists in the codebase, indicating the vulnerable code is present
  4. Verify the AJAX endpoint is accessible to unauthenticated users
    Check that the handler is registered with wp_ajax_nopriv_ hooks by searching for 'wp_ajax_nopriv_wppb_request_users_pins_action' in plugin files
    Affected if The hook is registered with wp_ajax_nopiv_, meaning unauthenticated users can trigger it
  5. Test if the vulnerable parameter is accepted
    Send a POST request to /wp-admin/admin-ajax.php with action=wppb_request_users_pins_action and a test args parameter (e.g., args=O:1:"A":0:{})
    Affected if The AJAX endpoint responds (even with an error) rather than returning 0 or rejecting the request outright

If Profile Builder Pro version 3.14.5 or lower is installed with the vulnerable AJAX handler registered for unauthenticated access, the environment is affected by this PHP Object Injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of Profile Builder Pro as soon as available. As a temporary measure, disable the plugin or deploy WAF rules to block the affected AJAX endpoint until a patch can be applied.

Recommended fix Moderate confidence

Profile Builder Pro version 3.14.6 or latest available version (contact vendor for exact fixed release)

  1. 1. Contact Cozmoslabs (the plugin developer) directly to request the latest security-patched version of Profile Builder Pro.
  2. 2. Alternatively, check the official Profile Builder Pro changelog or release notes for version 3.14.6 or higher which should contain the security fix.
  3. 3. Before applying the update to a production site, test the new version in a staging environment to ensure compatibility with your WordPress setup.
  4. 4. Apply the upgrade to the production site once testing is complete.
  5. 5. Verify the AJAX handler `wppb_request_users_pins_action_callback` is no longer vulnerable by confirming the `maybe_unserialize()` call on the 'args' POST parameter has been removed or properly sanitized.
Caveat Standard minor version upgrade; review changelog for any settings or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7647 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7647 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data