Zoho Crm Lead MagnetWordPress extension · Zohocorp

CVE-2022-41978

MEDIUM · 6.5 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to after 1.7.5.8 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
Auth. (subscriber+) Arbitrary Options Update vulnerability in Zoho CRM Lead Magnet plugin <= 1.7.5.8 on WordPress.

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

An authenticated arbitrary options update vulnerability in the Zoho CRM Lead Magnet plugin for WordPress allows users with subscriber-level privileges or higher to modify arbitrary WordPress options settings, potentially enabling privilege escalation to admin-level access.

MitigationUpdate the Zoho CRM Lead Magnet plugin to a version higher than 1.7.5.8, or deactivate/remove the plugin if no patched version 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
Zoho Crm Lead MagnetWordPress extension
Affected:<= 1.7.5.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
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 checks

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

  1. Confirm plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Zoho CRM Lead Magnet' or 'Zohocorp Zoho Crm Lead Magnet' in the list. Alternatively, check for the plugin directory at /wp-content/plugins/zoho-crm-lead-magnet/
    Affected if The plugin directory exists or the plugin appears in the WordPress plugins list
  2. Identify installed version
    In WordPress admin > Plugins > Installed Plugins, find the Zoho CRM Lead Magnet plugin and read the version number displayed beneath the plugin name. Compare this version to the affected range: any version <= 1.7.5.8
    Affected if The installed version is 1.7.5.8 or any lower version number
  3. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if the Zoho CRM Lead Magnet plugin has an 'Active' status or if the 'Activate' link is present. Check the plugin file header for 'Plugin Status: Active' or query the wp_options table for the active_plugins option
    Affected if The plugin is currently active and running on the site
  4. Audit WordPress options for unauthorized changes
    Review WordPress options in the database table wp_options (or via WP-CLI: wp option list --search='%user%' or wp option list --search='%role%'). Check for unexpected changes to options such as default_role, users_can_register, or new admin accounts
    Affected if Options have been modified to allow subscriber-level users elevated privileges, or new administrator accounts exist that were not created through standard WordPress admin processes

The site is affected if the Zoho CRM Lead Magnet plugin version 1.7.5.8 or lower is installed and active, regardless of whether unauthorized privilege escalation has already occurred.

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.

From vendor data
Upgrade available Upgrade to a release after 1.7.5.8
Interim mitigation

Update the Zoho CRM Lead Magnet plugin to a version higher than 1.7.5.8, or deactivate/remove the plugin if no patched version is available.

Fix this in Zoho Crm Lead Magnet Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41978 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41978 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