dbcve.org
User RegistrationWordPress extension · Wpeverest

CVE-2023-29429

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 2.3.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in WPEverest User Registration allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects User Registration: from n/a through 2.3.2.1.

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 · moderate confidence

A Missing Authorization vulnerability in the WPEverest User Registration WordPress plugin (versions through 2.3.2.1) allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized users to access or modify registration data they should not have permission to access.

MitigationUpgrade to User Registration version 2.3.3 or later which contains the authorization fix; ensure all WordPress installations and plugins are kept current.

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
User RegistrationWordPress extension
Affected:< 2.3.3

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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 User Registration plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'User Registration' by WPEverest, or check the wp-content/plugins/user-registration directory exists
    Affected if Plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find User Registration, and view the version number under the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/user-registration/user-registration.php for 'Version:'
    Affected if Version is 2.3.2.1 or earlier (any version below 2.3.3)
  3. Inspect user role capabilities for registration data access
    Navigate to User Registration > User Roles in the admin panel. Review which user roles have permissions to view, edit, or delete registration data and submissions
    Affected if Lower-privileged roles (such as Subscriber, Contributor, or custom roles) have elevated permissions to access or modify registration data they should not have access to
  4. Check access control settings for registration forms
    Navigate to User Registration > All Forms, select each form, and review the form settings under the General Options or Settings tab for any misconfigured visibility or access restrictions
    Affected if Forms are configured to allow unauthorized users to access or modify registration submissions beyond what their role should permit

A user is affected if the User Registration plugin version is below 2.3.3 and the access control settings or user role configurations allow unauthorized access to registration data.

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
Upgrade available Upgrade to 2.3.3 or later
Fixed in 2.3.3
Interim mitigation

Upgrade to User Registration version 2.3.3 or later which contains the authorization fix; ensure all WordPress installations and plugins are kept current.

Recommended fix High confidence

User Registration plugin version 2.3.3 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find the 'User Registration' plugin by WPEverest
  4. Check the current version installed
  5. If the installed version is below 2.3.3, click 'Update Now' to upgrade to version 2.3.3 or later
  6. After updating, verify the new version number in the plugins list
  7. Test user registration functionality to ensure the plugin continues to work correctly

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

Fix this in User Registration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29429 — 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-2023-29429 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