dbcve.org
Manageengine Password Manager ProApplication · Zohocorp

CVE-2020-9347

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Zoho ManageEngine Password Manager Pro through 10.x has a CSV Excel Macro Injection vulnerability via a crafted name that is mishandled by the Export Passwords feature. NOTE: the vendor disputes the significance of this report because they expect CSV risk mitigation to be provided by an external application, and do not plan to add CSV constraints to their own products

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

Zoho ManageEngine Password Manager Pro versions through 10.x contain a CSV Excel Macro Injection vulnerability in the Export Passwords feature. When password names contain special characters (=, +, -, @, etc.) that trigger formula interpretation in spreadsheet applications, the exported CSV can cause arbitrary command execution or data exfiltration when opened in Excel. The application fails to sanitize or encode these characters before CSV export.

MitigationImplement server-side input validation to escape or remove formula-initiating characters (=, +, -, @, tab, carriage return) from password names before CSV export, or switch to safer export formats like JSON that don't execute formulas. Users should also be warned about opening exported CSV files in spreadsheet applications.

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
Manageengine Password Manager ProApplication
Affected:= 10.0= 10.1= 10.2= 10.3= 10.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Password Manager Pro version
    Access the product administration console or check the installed software version. In the admin interface, navigate to the About or System Information section. Alternatively, check the installation directory for version files or use the product's built-in version lookup feature.
    Affected if The installed version is 10.0, 10.1, 10.2, 10.3, or 10.4 (or any 10.x version before the patch).
  2. Locate the Export Passwords feature
    Log into the Password Manager Pro administrative interface and navigate to the password management or export section. Identify if a CSV export option exists for password entries.
    Affected if The CSV export functionality is present and accessible in the product.
  3. Review password entries for special characters
    Examine the password repository for any password names or entries that contain formula-initiating characters: equals (=), plus (+), minus (-), at symbol (@), tab, or carriage return. Use the search or filter功能 in the password list view to identify these entries.
    Affected if Password entries exist with names containing any of these special characters: =, +, -, @, or whitespace characters.
  4. Inspect exported CSV files for unsanitized characters
    If CSV exports have been performed, locate any exported CSV files. Open them in a text editor (not Excel) and inspect whether password names containing formula-triggering characters appear as raw characters or are escaped (for example, leading single quote or encoded format).
    Affected if The exported CSV contains unescaped formula-initiating characters (=, +, -, @) in password name fields when opened in a text editor.
  5. Test export with a controlled special-character password
    Create a test password entry with a name starting with '=' followed by a formula (such as =cmd|' /C calc'!A0). Export this entry to CSV and examine the output in a text editor.
    Affected if The exported CSV preserves the '=' and subsequent characters without escaping or encoding, allowing formula injection.

A user is affected if Password Manager Pro version 10.x is in use, the CSV export feature exists, and password names contain unescaped formula-triggering characters (=, +, -, @) that appear raw in exported CSV files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side input validation to escape or remove formula-initiating characters (=, +, -, @, tab, carriage return) from password names before CSV export, or switch to safer export formats like JSON that don't execute formulas. Users should also be warned about opening exported CSV files in spreadsheet applications.

Fix this in Manageengine Password Manager Pro 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 help mitigating

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-2020-9347 — 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-2020-9347 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