dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-4958

HIGH · 7.1 CVSS v3.1 Published 2024-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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 User Registration – Custom Registration Form, Login Form, and User Profile WordPress Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'import_form_action' function in versions up to, and including, 3.2.0.1. This makes it possible for authenticated attackers, with contributor-level permissions and above, to import a registration form with a default user role of administrator. If an administrator approves or publishes a post or page with the shortcode to the imported form, any user can register as an administrator.

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 User Registration WordPress plugin lacks a capability check on the import_form_action function, allowing authenticated users with contributor-level permissions to import registration forms configured with administrator as the default user role. When an administrator publishes content containing the shortcode for this imported form, any site visitor can register with administrator privileges, achieving full privilege escalation.

MitigationUpdate the plugin to a version beyond 3.2.0.1 that implements proper capability verification on the import_form_action function, or remove the plugin if no patched version is available.

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

CVSS:3.1/AV:N/AC:H/PR:L/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 checks

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

  1. Verify User Registration plugin is installed
    Access WordPress admin under Plugins > Installed Plugins, or use command line: ls wp-content/plugins/ | grep user-registration, or run: wp plugin list --status=active --format=json
    Affected if Plugin is not installed or not active - not vulnerable
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > User Registration, or check version in plugin main file header, or run: wp plugin get user-registration --field=version
    Affected if Version is 3.2.0.1 or lower - potentially vulnerable; version is unknown but plugin exists - continue to next check
  3. Confirm import_form_action function lacks capability check
    Inspect the plugin file containing import_form_action (typically in includes/functions/*.php or similar), look for add_action("wp_ajax_import_form_action", ...) without current_user_can() or capability check before processing
    Affected if Function exists and processes import without verifying user capabilities - vulnerable
  4. Verify contributor-level users exist with access
    In WordPress admin under Users > All Users, check for users with Contributor role, or run: wp user list --role=contributor --format=count
    Affected if Contributor users exist - they can trigger the import function; no contributors - lower risk but plugin still has the flaw
  5. Check for registration forms with administrator as default role
    In User Registration plugin settings, navigate to User Registration > All Forms > select each form > Form Settings > login options, verify if any form has Administrator selected as the default user role for registration
    Affected if A form exists with Administrator as the default role - the complete exploit chain is possible

User is affected if the User Registration plugin is installed and active with version 3.2.0.1 or lower, the import_form_action function lacks capability verification, and either contributor-level users exist or forms with administrator role are configured.

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 the plugin to a version beyond 3.2.0.1 that implements proper capability verification on the import_form_action function, or remove the plugin if no patched version is available.

Recommended fix Moderate confidence

Latest version after 3.2.0.1 (check WordPress plugin repository for 3.2.0.2 or later)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find 'User Registration – Custom Registration Form, Login Form, and User Profile'
  4. 4. Check the current version installed
  5. 5. If the installed version is 3.2.0.1 or below, update the plugin to the latest available version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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