Auto Login New User After RegistrationWordPress extension · Auto Login New User After Registration Project
CVE-2023-46202
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 Jeff Sherk Auto Login New User After Registration plugin <= 1.9.6 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 Jeff Sherk Auto Login New User After Registration WordPress plugin versions 1.9.6 and below allows attackers to trick authenticated administrators or users into triggering unintended registration or login actions via crafted requests.
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
Auto Login New User After RegistrationWordPress extension
<= 1.9.6CVSS 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.
-
Locate the plugin installation directoryCheck for the presence of the 'auto-login-new-user-after-registration' folder in your WordPress installation under wp-content/plugins/Affected if The plugin folder exists in the plugins directory
-
Read the main plugin file for version informationOpen the primary PHP file in the plugin directory (usually auto-login-new-user-after-registration.php) and locate the 'Version' header in the plugin comments at the top of the fileAffected if The version string shows 1.9.6 or lower
-
Confirm the plugin is activeIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and verify whether 'Auto Login New User After Registration' is listed as ActiveAffected if The plugin shows an 'Activate' or 'Network Activate' link rather than 'Deactivate' (plugin is not currently enabled)
-
Check for CSRF protection in plugin codeExamine the plugin PHP files for the presence of wp_nonce_field(), wp_verify_nonce(), or 'nonce' in form submissions - the absence of these nonces indicates the vulnerability is presentAffected if No CSRF nonces are found in registration or login form handling code
You are affected if the plugin is installed, active, and the version is 1.9.6 or lower (or if no anti-CSRF nonces are found in the code regardless of version).
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.
From vendor dataUpdate the plugin to the latest version which should include proper anti-CSRF token validation (nonces) on registration/login forms and actions, and implement SameSite cookie attributes.
Fix this in Auto Login New User After Registration
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-46202 — 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-46202 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