dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-5785

HIGH · 8.1 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
Zohocorp ManageEngine PAM360 versions before 8531 and ManageEngine Password Manager Pro versions from 8600 to 13230 are vulnerable to Authenticated SQL injection in the query report module.

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

Authenticated SQL injection vulnerability in the query report module of ManageEngine PAM360 (versions before 8531) and Password Manager Pro (versions 8600-13230). An attacker with valid credentials can inject malicious SQL queries through the module to potentially access, modify, or delete sensitive data in the underlying database.

MitigationApply vendor patches: upgrade PAM360 to version 8531 or later, and Password Manager Pro to version 13231 or later. Prioritize patching for systems accessible from less-trusted networks.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify installed product
    Determine whether your environment has ManageEngine PAM360 or ManageEngine Password Manager Pro installed. Check the application name displayed in the product web interface or service information.
    Affected if The product is either PAM360 or Password Manager Pro and matches the version criteria.
  2. Check PAM360 version
    Locate the installed version number for PAM360. This is typically visible in the product web interface under the 'About' or 'Help' section, or can be found in the installation directory version file. Compare your version against 8531.
    Affected if PAM360 version is earlier than 8531.
  3. Check Password Manager Pro version
    Locate the installed version number for Password Manager Pro. This is typically visible in the product web interface under the 'About' or 'Help' section, or in the installation directory. Compare your version against the range 8600-13230.
    Affected if Password Manager Pro version falls between 8600 and 13230 inclusive.
  4. Verify query report module access
    Confirm that the query report functionality is enabled and accessible to authenticated users in your deployment. Check user role permissions to see if standard users or specific roles can access the reports or query builder feature.
    Affected if The query report module is accessible to authenticated users in your environment.
  5. Review database query logs
    Inspect database query logs or audit trails for the PAM360 or Password Manager Pro application. Look for unusual or suspicious SQL statements, especially those containing UNION SELECT, OR 1=1, or other SQL injection patterns originating from the query report functionality.
    Affected if Suspicious SQL patterns are found in logs originating from the query report feature.

You are affected if you run PAM360 version below 8531 or Password Manager Pro version 8600-13230, and the query report module is accessible to authenticated users in your environment.

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

Apply vendor patches: upgrade PAM360 to version 8531 or later, and Password Manager Pro to version 13231 or later. Prioritize patching for systems accessible from less-trusted networks.

Recommended fix Moderate confidence

PAM360: version 8531 or later; Password Manager Pro: latest version beyond 13230

  1. 1. Identify the current version of ManageEngine PAM360 or Password Manager Pro installed in your environment.
  2. 2. For PAM360: Upgrade to version 8531 or later.
  3. 3. For Password Manager Pro: Upgrade to the latest available version beyond 13230.
  4. 4. After upgrading, verify the SQL injection vulnerability is resolved by reviewing release notes or testing in a non-production environment.
  5. 5. Apply the upgrade during a planned maintenance window following standard change management procedures.
Caveat Review release notes for any configuration or feature changes between your current version and the target version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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