Ultimate Addons For ElementorWordPress extension · Brainstormforce
CVE-2020-13125
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 · uneditedAn issue was discovered in the "Ultimate Addons for Elementor" plugin before 1.24.2 for WordPress, as exploited in the wild in May 2020 in conjunction with CVE-2020-13126. Unauthenticated attackers can create users with the Subscriber role even if registration is disabled.
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 Ultimate Addons for Elementor plugin before version 1.24.2 contains an authentication bypass allowing unauthenticated attackers to create WordPress user accounts with Subscriber role via the plugin's AJAX actions, even when user registration is disabled in WordPress settings.
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
Ultimate Addons For ElementorWordPress extension
< 1.24.2CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Verify Ultimate Addons for Elementor plugin versionNavigate to WordPress Dashboard > Plugins > Installed Plugins. Locate 'Ultimate Addons for Elementor' by Brainstormforce and check the version number displayed. Alternatively, inspect the main plugin file header or check the version in the plugin's main PHP file.Affected if The installed version is below 1.24.2 (for example, 1.24.1, 1.24.0, or earlier).
-
Inspect WordPress user accounts for unknown subscribersNavigate to WordPress Dashboard > Users > All Users. Review the list of user accounts, paying particular attention to accounts with the 'Subscriber' role that you do not recognize. Note the user login, email, and date of registration.Affected if There are Subscriber accounts present that were created without your knowledge or authorization, especially those created around the time the vulnerability was active.
-
Check user registration settings in WordPressNavigate to WordPress Dashboard > Settings > General and verify the 'Membership' setting 'Anyone can register' - note its current state for context, but remember this bypass works even when registration is disabled.Affected if This check provides context; the vulnerability allows account creation regardless of this setting, so a 'disabled' setting does not mean you are unaffected if unauthorized accounts exist.
You are affected if the Ultimate Addons for Elementor plugin version is below 1.24.2 AND you discover unauthorized Subscriber accounts in your WordPress user database that you did not create.
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 data1.24.2
Update the Ultimate Addons for Elementor plugin to version 1.24.2 or later immediately, then audit WordPress user accounts for unauthorized Subscriber accounts and remove any suspicious newly created accounts.
Fix this in Ultimate Addons For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13125 — 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-2020-13125 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