dbcve.org
YouzifyWordPress extension · Kainelabs

CVE-2023-47191

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 1.2.3 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Authorization Bypass Through User-Controlled Key vulnerability in KaineLabs Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress.This issue affects Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress: from n/a through 1.2.2.

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

This is an authorization bypass vulnerability in the Youzify WordPress plugin where an attacker can manipulate a user-controlled key parameter to gain unauthorized access to functions or data they shouldn't have access to. The vulnerability exists in versions up to 1.2.2 and allows bypassing proper authorization checks.

MitigationUpdate Youzify plugin to the latest patched version. If no update is available, review the plugin code for authorization logic that trusts user-supplied input for access decisions and implement proper access controls.

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.3

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Verify Youzify plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'Youzify' and check the version number displayed. Alternatively, inspect the main plugin file (youzify.php) in wp-content/plugins/youzify/ and look for the 'Version:' header in the plugin comments.
    Affected if The installed version is less than 1.2.3 (e.g., 1.2.2, 1.2.1, 1.2.0, etc.)
  2. Confirm plugin is active
    In the WordPress Plugins admin page, verify whether Youzify is currently activated. An inactive plugin with a vulnerable version may not be exploitable.
    Affected if Youzify is active and the version is below 1.2.3
  3. Identify accessible endpoints using user-supplied key parameters
    Review the plugin's publicly accessible AJAX actions and front-end endpoints. Check PHP files in wp-content/plugins/youzify/includes/ for functions that process $_GET or $_POST parameters named 'key' or similar user-controlled inputs without proper capability checks. Search for 'capability' or 'current_user_can' calls that follow the key parameter usage.
    Affected if The plugin exposes any public-facing functions that rely on a key parameter for access decisions without validating user permissions
  4. Check WordPress user role permissions for Youzify features
    Go to WordPress admin > Youzify Settings (if available). Review which user roles (Administrator, Editor, Author, Subscriber, etc.) have access to Youzify features like user profiles, activity feeds, or membership functions.
    Affected if Lower-privileged roles (like Subscriber) have access to features that should be restricted to higher-privileged users, and the vulnerable version is in use

You are affected if Youzify plugin version is below 1.2.3 and the plugin is active with any publicly accessible endpoints that use user-controlled key parameters for authorization decisions.

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.3 or later
Fixed in 1.2.3
Interim mitigation

Update Youzify plugin to the latest patched version. If no update is available, review the plugin code for authorization logic that trusts user-supplied input for access decisions and implement proper access controls.

Recommended fix High confidence

1.2.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Youzify plugin in the list
  4. Click on 'Update now' if an update is available, or delete the current version and upload version 1.2.3
  5. Alternatively, update via Dashboard > Updates or using a plugin management tool
  6. After updating, verify the plugin version shows 1.2.3 in the Plugins list
  7. Test that BuddyPress profile and membership functionality works correctly

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

Fix this in Youzify Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47191 — 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-2023-47191 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