dbcve.org
YouzifyWordPress extension · Kainelabs

CVE-2024-4742

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to after 1.2.5 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
The Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress plugin for WordPress is vulnerable to SQL Injection via the order_by shortcode attribute in all versions up to, and including, 1.2.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 confidence

The Youzify WordPress plugin fails to properly sanitize and escape the order_by shortcode attribute parameter before using it in an SQL query. An authenticated attacker with Contributor-level access or higher can inject malicious SQL queries through this parameter to exfiltrate sensitive data from the database.

MitigationUpdate the Youzify plugin to version 1.2.6 or later which contains the security patch for this SQL injection vulnerability.

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

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 is installed
    Access WordPress admin dashboard, go to Plugins > Installed Plugins. Look for 'Youzify' or 'Youzify - BuddyPress Community' in the list of active plugins.
    Affected if Youzify plugin appears in the WordPress plugins list and is active.
  2. Check installed Youzify version
    In WordPress admin, go to Plugins > Installed Plugins. Click on the Youzify plugin to view details, or check the plugin's main PHP file (usually youzify.php) for the 'Version' header in the file comment block.
    Affected if The installed version is 1.2.5 or lower.
  3. Confirm shortcode usage capability
    Verify that the site allows authenticated users with Contributor-level or higher access to create or edit content containing shortcodes. Check if the [youzify] shortcode is registered and available by viewing plugin source code for add_shortcode('youzify', ...) function.
    Affected if The Youzify shortcode is registered and the site permits contributor-level users to insert shortcodes in posts/pages.
  4. Identify vulnerable parameter usage
    Search plugin source code for the SQL query that uses the order_by parameter. Look in the plugin's main file or related PHP files for queries containing $order_by or $_GET/$_POST['order_by'] directly in SQL statements without proper prepared statements or sanitization.
    Affected if Code inspection reveals the order_by parameter is used in SQL queries without prepared statements or $wpdb->prepare() with proper placeholder escaping.

A site is affected if Youzify plugin version 1.2.5 or lower is installed and active, and the order_by shortcode parameter can be manipulated by authenticated users.

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 a release after 1.2.5
Interim mitigation

Update the Youzify plugin to version 1.2.6 or later which contains the security patch for this SQL injection vulnerability.

Recommended fix Moderate confidence

Youzify version 1.2.6 or later (check WordPress plugin repository for latest available version)

  1. Check the WordPress plugin repository for Youzify to identify if a newer version than 1.2.5 has been released
  2. If a newer version (typically 1.2.6 or higher) is available, navigate to Plugins > Add New > Upload in WordPress admin
  3. Deactivate and delete the current Youzify plugin installation
  4. Upload and install the newer fixed version of Youzify
  5. Reactivate the plugin
  6. Verify the order_by shortcode functionality works correctly after the update
  7. Ensure users with Contributor-level or higher access are aware of proper parameter handling if needed
Caveat Before upgrading, review the plugin's changelog to check for any changes that might affect site functionality or theme compatibility

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

Fix this in Youzify Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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