dbcve.org
YouzifyWordPress extension · Kainelabs

CVE-2024-39635

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.2.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Missing Authorization vulnerability in KaineLabs Youzify allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Youzify: from n/a through 1.2.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 confidence

A missing authorization vulnerability in KaineLabs Youzify WordPress plugin allows attackers to exploit incorrectly configured access control security levels. This enables unauthorized users to access functionality they should not have permission to use, likely due to missing capability checks or improper role validation in plugin functions.

MitigationApply available security patches for Youzify (upgrade to latest version if patched), or implement proper authorization checks (nonce verification and capability checks) on all sensitive plugin functions. If no patch exists, disable the plugin until a fix is available.

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
Affected:< 1.2.8

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Youzify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Youzify' or 'Kainelabs Youzify' in the list. Alternatively, check the /wp-content/plugins/youzify directory exists on the server.
    Affected if Youzify plugin is present in the WordPress installation
  2. Check installed Youzify version
    In WordPress admin, go to Plugins > Installed Plugins and find the Youzify plugin entry. The version number is displayed below the plugin name. Alternatively, check the version in /wp-content/plugins/youzify/youzify.php header comment or in the WordPress plugins database table.
    Affected if Version is lower than 1.2.8 (e.g., 1.2.7, 1.2.6, etc.)
  3. Verify WordPress user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is checked. Or query the wp_options table for 'users_can_register' setting.
    Affected if User registration is enabled and Youzify version is below 1.2.8
  4. Review Youzify role configuration
    In WordPress admin, go to Youzify settings and examine the 'Role Settings' or 'Member Types' configuration. Check if default user roles are assigned to new registrations.
    Affected if Youzify is configured to assign roles to new users and version is below 1.2.8

You are affected if Youzify plugin is installed with a version lower than 1.2.8 and user registration or social features are enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.2.8 or later
Fixed in 1.2.8
Interim mitigation

Apply available security patches for Youzify (upgrade to latest version if patched), or implement proper authorization checks (nonce verification and capability checks) on all sensitive plugin functions. If no patch exists, disable the plugin until a fix is available.

Recommended fix High confidence

Youzify version 1.2.8

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. Locate Youzify plugin in the list
  4. Click 'Update now' if an update is available, or manually upload version 1.2.8 of the Youzify plugin
  5. Verify the plugin updated successfully by checking the installed version
  6. Clear any caching mechanisms (site cache, CDN cache) after updating
  7. Test Youzify functionality to ensure the plugin works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Youzify Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39635 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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