Profile BuilderWordPress extension · Cozmoslabs
CVE-2023-47669
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin <= 3.10.3 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the User Profile Builder WordPress plugin allows attackers to trick authenticated administrators into unknowingly submitting malicious requests (such as modifying user roles or account settings) by exploiting the lack of anti-CSRF tokens on sensitive form actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Profile BuilderWordPress extension
< 3.10.4CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Profile Builder plugin is installedCheck the WordPress plugins directory (wp-content/plugins/profile-builder/) or review the Plugins page in WordPress admin for 'Profile Builder' by CozmoslabsAffected if The plugin is present and active in the WordPress installation
-
Identify the installed version numberLocate the plugin version in the main PHP file header (e.g., profile-builder/index.php) or in the plugin's readme.txt file under the 'Stable tag' fieldAffected if The version is listed as lower than 3.10.4 (e.g., 3.10.3, 3.9.x, etc.)
-
Verify admin user access existsCheck WordPress users with Administrator role by navigating to Users > All Users in the admin dashboard or querying wp_users table for wp_capabilities containing 'administrator'Affected if At least one administrator account exists and can access the Profile Builder settings
-
Confirm user management forms are accessibleNavigate to Profile Builder settings pages (typically under Users > Profile Builder in admin), specifically pages containing user role assignment or account registration settingsAffected if Forms for modifying user roles, registration settings, or user fields are present and accessible to administrators
The environment is affected if Profile Builder plugin versions below 3.10.4 are installed with active administrator accounts able to access user management forms lacking CSRF token protection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.10.4
Update the User Profile Builder plugin to version 3.10.4 or later which implements proper CSRF token validation for state-changing operations.
Profile Builder version 3.10.4
- Backup your WordPress site database and files before making any changes
- Navigate to WordPress admin dashboard > Plugins section
- Locate Profile Builder plugin in the installed plugins list
- Click 'Update now' on Profile Builder when version 3.10.4 is available, or manually upload version 3.10.4
- Verify the update completed successfully and the plugin shows version 3.10.4 or higher
- Test user registration and profile functionality to ensure the plugin continues to work correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Profile Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47669 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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