ConvertplusWordPress extension · Convertplug
CVE-2019-15863
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 · uneditedThe ConvertPlus plugin before 3.4.5 for WordPress has an unintended account creation (with the none role) via a request for variants.
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 confidenceThe ConvertPlus WordPress plugin before version 3.4.5 contains an access control flaw that allows unintended account creation through variant requests. The plugin incorrectly creates user accounts without proper authorization checks, assigning them the 'none' role which provides no privileges but still constitutes unauthorized account creation.
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
ConvertplusWordPress extension
< 3.4.5CVSS 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
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Verify ConvertPlus plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/convertplug directory existenceAffected if ConvertPlus plugin is present in the WordPress installation
-
Check installed ConvertPlus versionIn WordPress admin, go to Plugins > Installed Plugins and locate ConvertPlus to view the version number, or check the main plugin file header for the Version fieldAffected if Version is displayed as lower than 3.4.5 or the version field is missing/unreadable and the plugin is active
-
Identify user accounts with none roleIn WordPress admin, go to Users > All Users and look for any user accounts with the role column showing 'None' or an unrecognized roleAffected if Any user account exists with 'None' role that was not deliberately created by an administrator for a specific purpose
-
Review user creation logs if availableCheck WordPress audit logs, server access logs, or security plugins for POST requests to /wp-admin/admin-ajax.php with action 'cps_create_user' or similar registration-related actions originating from unauthenticated IPsAffected if Unauthenticated or unexpected user creation events are logged in the timeframe the plugin was active
The environment is affected if ConvertPlus plugin version is below 3.4.5 and unauthorized user accounts with 'None' role exist or unauthenticated user creation requests are logged.
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 data3.4.5
Update the ConvertPlus plugin to version 3.4.5 or later to obtain the patched version that includes proper authorization validation before user account creation.
Fix this in Convertplus
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15863 — 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-2019-15863 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