YouzifyWordPress extension · Kainelabs
CVE-2024-13370
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 Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the save_addon_key_license() function in all versions up to, and including, 1.3.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options to a value of a valid license key.
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 Youzify WordPress plugin has a broken access control vulnerability where the save_addon_key_license() function lacks a capability check. This allows any authenticated user with Subscriber-level privileges or higher to update arbitrary WordPress options to arbitrary license key values, potentially enabling privilege escalation or site compromise.
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
YouzifyWordPress extension
<= 1.3.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check if Youzify plugin is installed and activeIn WordPress admin, go to Plugins > Installed Plugins and look for 'Youzify' by Kainelabs. Note whether it is active or inactive.Affected if The Youzify plugin is installed and active (inactive plugins still have vulnerable code but cannot be exploited)
-
Determine installed Youzify versionIn WordPress admin, go to Plugins > Installed Plugins, find Youzify, and note the version number displayed. Compare it to the affected range: versions 1.3.3 and below are vulnerable.Affected if The installed version is 1.3.3 or lower
-
Check if user registration is enabledIn WordPress admin, go to Settings > General and look for the 'Membership' setting 'Anyone can register'. If enabled, anyone can create a Subscriber-level account.Affected if User registration is enabled, allowing creation of Subscriber-level accounts that can exploit this flaw
-
Review WordPress options for unauthorized changesUse a database query or plugin to inspect the wp_options table, specifically looking for license_key or similar option values that were modified unexpectedly. Check for any options set to suspicious license key strings.Affected if Options table contains license key values that were changed without administrator action, indicating possible exploitation
You are affected if the Youzify plugin version is 1.3.3 or lower AND user registration is enabled, allowing any logged-in user to modify WordPress options through the vulnerable function.
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 to version 1.3.4 or later which includes proper capability verification. Until patched, restrict user registration or disable the plugin.
Fix this in Youzify
Scoped from the published advisory
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13370 — 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-2024-13370 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