Auto Login New User After RegistrationWordPress extension · Auto Login New User After Registration Project
CVE-2023-46201
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 allows Stored XSS.This issue affects Auto Login New User After Registration: from n/a through 1.9.6.
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 confidenceThis is a CSRF vulnerability in the WordPress plugin 'Auto Login New User After Registration' that allows attackers to inject stored XSS payloads. The lack of anti-CSRF token validation on registration forms enables attackers to trick authenticated administrators into unknowingly submitting malicious requests that persist malicious scripts in the application.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Auto Login New User After Registration' in the listAffected if the plugin appears in the installed plugins list
-
Identify installed versionIn the plugins list, view the plugin details or check the plugin header in its main PHP file to determine the version numberAffected if the installed version is 1.9.6 or lower
-
Inspect registration form handlingExamine the plugin PHP files that handle user registration submissions, specifically looking for nonce verification or token validation calls before processing registration dataAffected if no nonce validation is found before processing registration form data
-
Search for malicious user dataQuery the WordPress user meta or usermeta table for any suspicious script tags, HTML, or JavaScript payloads in user registration fields such as username, display name, or custom registration fieldsAffected if any user accounts contain XSS payloads like <script> tags or event handlers in user metadata
A user is affected if the Auto Login New User After Registration plugin version is 1.9.6 or lower and the registration form lacks nonce validation, or if malicious XSS payloads are found in user data.
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 dataImplement nonce/token validation on all state-changing operations in the plugin and update to the latest patched version when available. Site administrators should review user registrations for malicious XSS payloads.
Fix this in Auto Login New User After Registration
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46201 — 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-46201 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