Skip to content
major vulnerability· requires attention

Affects widely-used ManageEngine PAM360/Password Manager Pro; authenticated SQLi could expose sensitive data, impacting multiple enterprises.

Web

CVE-2026-5785

8.1
High
EPSS 1%Patch availableApr 16, 2026

Authenticated SQL injection in PAM360/Password Manager Pro report module.

common questions

Is CVE-2026-5785 being exploited?

Not confirmed. CVE-2026-5785 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.4% probability of exploitation in the next 30 days.

How severe is CVE-2026-5785?

CVE-2026-5785 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-5785?

Yes. A fix has been recorded for CVE-2026-5785. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-5785 affect?

CVE-2026-5785 affects ManageEngine PAM360 (pre-8531), ManageEngine Password Manager Pro (8600-13230). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-5785?

Upgrade to patched versions 8531+ (PAM360) and 13230+ (Password Manager Pro).

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ManageEngine PAM360 (pre-8531)ManageEngine Password Manager Pro (8600-13230)
impact

Authenticated attacker can exfiltrate sensitive DB data via report module by SQL payloads.

action required

Immediate action required

affected versions
Zohocorp ManageEngine PAM360
  • affected< 8531
Zohocorp ManageEngine Password Manager Pro
  • affected>= 8600 and <= 13230

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free