CVE-2026-8174
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 · uneditedZohocorp Zoho Mail wordpress plugin is vulnerable to Cross-Site request forgery (CSRF). This issue affects Zoho Mail wordpress plugin versions before 1.6.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 confidenceThe Zoho Mail WordPress plugin before version 1.6.2 is vulnerable to Cross-Site Request Forgery (CSRF), allowing attackers to trick authenticated administrators into performing unintended actions through maliciously crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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.
-
Locate the Zoho Mail plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Zoho Mail' in the list. The version number is displayed below the plugin name.Affected if The displayed version is any version prior to 1.6.2 (for example, 1.6.1, 1.6.0, 1.5.0, etc.)
-
Verify via plugin filesIf you have file system access, check the plugin main file (usually wp-content/plugins/zoho-mail/zm-mail.php or similar) for the 'Version' header in the plugin comment block, or check the readme.txt file for the version number.Affected if The version header shows a number lower than 1.6.2
-
Check if plugin settings are accessibleNavigate to the Zoho Mail plugin settings page in WordPress admin (usually under Settings > Zoho Mail). Try to identify forms that modify plugin configuration.Affected if Settings forms exist and the plugin version is below 1.6.2, making CSRF exploitation possible
-
Review nonce implementationIf you can access the plugin source code, inspect PHP files that handle settings changes. Look for wp_verify_nonce or check_admin_referer calls in functions that process form submissions.Affected if No nonce verification is found in settings-handling code AND the plugin version is prior to 1.6.2
You are affected if the Zoho Mail WordPress plugin is installed with any version prior to 1.6.2 and the plugin settings can be modified by an authenticated administrator.
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.
dbcve · scopedUpdate the Zoho Mail WordPress plugin to version 1.6.2 or later to remediate this CSRF vulnerability.
1.6.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Zoho Mail plugin in the list
- If an update is available, click 'Update Now' to install the latest version
- Alternatively, go to Dashboard > Updates and apply available updates
- After updating, verify the plugin version is 1.6.2 or later by checking the plugin details
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8174 — 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-2026-8174 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