dbcve.org
Manageengine Applications ManagerApplication · Zohocorp

CVE-2025-27930

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-23
Fix available
A fix is available. Upgrade to 17.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Applications Manager versions 176600 and prior are vulnerable to stored cross-site scripting in the File/Directory monitor.

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 confidence

Stored cross-site scripting (XSS) vulnerability in the File/Directory monitor of Zohocorp ManageEngine Applications Manager versions 176600 and prior allows authenticated attackers to inject malicious JavaScript through unsanitized input fields in the monitor configuration.

MitigationUpgrade to a version beyond 176600 and implement proper input validation and output encoding on all File/Directory monitor parameters to prevent script injection.

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 Applications ManagerApplication
Affected:< 17.6= 17.6

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Applications Manager version
    Access the admin console and navigate to About or Settings to view the installed version number. Alternatively, check the build file or installation directory for version metadata.
    Affected if The installed version is 176600 or any version below 17.6 (e.g., 17.5, 17.4, earlier releases)
  2. Locate File/Directory monitor configuration
    In the Applications Manager console, navigate to Monitors or Add Monitor and identify if any File/Directory monitor profiles are created. Check the monitor list for entries showing FileMonitor or DirectoryMonitor type.
    Affected if One or more File/Directory monitor configurations exist in the system
  3. Inspect File/Directory monitor input fields
    Open each File/Directory monitor configuration and examine fields such as Directory Path, File Name, Filter Pattern, or any text input parameters. Look for unsanitized special characters or potential script tags in existing values.
    Affected if Any input fields in the File/Directory monitor contain raw user-supplied text without encoding or contain suspicious patterns like <script, javascript:, or event handlers
  4. Review audit logs for monitor creation
    Check the Applications Manager audit or activity logs for recent File/Directory monitor creations or modifications. Look for entries showing who created or modified these monitors.
    Affected if You find recent File/Directory monitor configuration changes you do not recognize

You are affected if your ManageEngine Applications Manager version is 176600 or below 17.6 AND you have any File/Directory monitors configured with unsanitized input in their configuration fields.

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
Upgrade available Upgrade to 17.6 or later
Fixed in 17.6
Interim mitigation

Upgrade to a version beyond 176600 and implement proper input validation and output encoding on all File/Directory monitor parameters to prevent script injection.

Recommended fix Moderate confidence

Any version newer than 17.6 (e.g., 17.7 or later)

  1. 1. Back up the current Applications Manager installation and database
  2. 2. Download the latest version of ManageEngine Applications Manager from the official vendor website
  3. 3. Stop the Applications Manager service before upgrading
  4. 4. Install/run the upgrade installer on the same server
  5. 5. Start the Applications Manager service after upgrade completes
  6. 6. Verify the File/Directory monitor functionality works correctly
  7. 7. Confirm the XSS vulnerability is resolved by testing the File/Directory monitor with appropriate input
Caveat Review release notes for any configuration or feature changes between your current version and the new version

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

Fix this in Manageengine Applications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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