dbcve.org
Simplr Registration Form Plus\+WordPress extension · Mikevanwinkle

CVE-2023-4213

HIGH · 8.8 CVSS v3.1 Published 2023-09-13
Fix available
A fix is available. Upgrade to after 2.4.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Simplr Registration Form Plus+ plugin for WordPress is vulnerable to Insecure Direct Object References in versions up to, and including, 2.4.5. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources. This makes it possible for authenticated attackers with subscriber-level permissions or above to change user passwords and potentially take over administrator accounts.

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 Simplr Registration Form Plus+ WordPress plugin (versions up to 2.4.5) contains an Insecure Direct Object Reference vulnerability that allows authenticated users with subscriber-level permissions to access and modify arbitrary user objects. Specifically, the plugin does not properly validate user authorization when processing password change requests, enabling attackers to reset passwords for any user account including administrators.

MitigationUpdate the plugin to version 2.4.6 or later which contains the security fix. If no update is available, remove the plugin immediately. As a precautionary measure, review user accounts for unauthorized changes and consider resetting administrator passwords.

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
Simplr Registration Form Plus\+WordPress extension
Affected:<= 2.4.5

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

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Simplr Registration Form Plus+' or 'Mikevanwinkle Simplr Registration Form Plus+' in the list of active plugins
    Affected if The plugin appears in the installed plugins list and is activated
  2. Check installed version
    In the Plugins page, locate the Simplr Registration Form Plus+ entry and note the version number displayed below the plugin name. Compare this version to the affected range: any version 2.4.5 or earlier is vulnerable
    Affected if The installed version is 2.4.5 or lower
  3. Confirm password change feature is accessible
    Navigate to the plugin settings (usually under Settings > Simplr Registration or similar) and verify that password change/reset functionality is enabled. Also check if the plugin exposes any endpoints for password modification
    Affected if Password change or reset features are enabled and accessible to logged-in users
  4. Review subscriber-level user accounts
    Go to Users > All Users in WordPress admin and examine which users have the 'Subscriber' role. The vulnerability allows any subscriber to reset passwords for administrator accounts
    Affected if There are subscriber-level accounts present in the system, creating the attack vector

If the Simplr Registration Form Plus+ plugin version 2.4.5 or lower is installed and active with password change functionality enabled, your environment is affected by this 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
Upgrade available Upgrade to a release after 2.4.5
Interim mitigation

Update the plugin to version 2.4.6 or later which contains the security fix. If no update is available, remove the plugin immediately. As a precautionary measure, review user accounts for unauthorized changes and consider resetting administrator passwords.

Recommended fix High confidence

Version 2.4.6 or later (latest available version)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'Simplr Registration Form Plus+' in the plugin list
  4. If an update is available, click 'Update Now'
  5. Alternatively, download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is functioning correctly

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

Fix this in Simplr Registration Form Plus\+ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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