VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

Profile Builder 4.0.0 — 4.0.4 - Authenticated (Subscriber+) Comment reCAPTCHA Protection Bypass

CVE-2026-111965Published · Updated

Action summary

Affected: 4.0.0 – 4.0.4Update to 4.0.5 or newer

All remediation steps
Watch plugin
Severity
Medium4.3
CVSS
4.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-804 Guessable CAPTCHA
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor profile-builder

  1. Affected4.0.0 – 4.0.4
  2. Patched in4.0.5

Update to 4.0.5 or newer.

You are affected if you run 4.0.0 – 4.0.4. Version 4.0.5 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 4.0.5, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Naoki Kawahigashi.

The Profile Builder plugin for WordPress is vulnerable to Security Feature Bypass in versions 4.0.0 through 4.0.4. This is due to missing enforcement of reCAPTCHA verification for comment submissions arriving via XML-RPC or the REST API in the wppb_verify_recaptcha_default_wp_comments and wppb_verify_turnstile_default_wp_comments functions. This makes it possible for authenticated attackers, with subscriber-level access and above, to bypass the reCAPTCHA anti-spam protection on the WordPress comment form by submitting comments via the XML-RPC or REST API, circumventing the configured CAPTCHA entirely. The reCAPTCHA or Turnstile field must be enabled for the default WordPress comment form in the plugin settings.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor

All 59
More vulnerabilities in User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Information Exposure
≤4.0.6Update to 4.0.7
CVE-2026-125777
Medium6.3Authenticated (Contributor+) Privilege Escalation
≤4.0.5Update to 4.0.6
CVE-2026-54854
High7.2Unauthenticated Stored Cross-Site Scripting
≤4.0.5Update to 4.0.6
CVE-2026-54855
Medium5.3Missing Authorization
≤4.0.5Update to 4.0.6
CVE-2026-54853
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
<4.0.5Update to 4.0.5
CVE-2026-111966

Timeline

  1. CVE published

    Severity medium, CVSS 4.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?