CVE-2018-11808
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 · uneditedIncorrect Access Control in CustomFieldsFeedServlet in Zoho ManageEngine Applications Manager Version 13 before build 13740 allows an attacker to delete any file and read certain files on the server in the context of the user (which by default is "NT AUTHORITY / SYSTEM") by sending a specially crafted request to the server.
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 confidenceZoho ManageEngine Applications Manager version 13 before build 13740 contains an incorrect access control vulnerability in the CustomFieldsFeedServlet component. The vulnerability allows unauthenticated attackers to send specially crafted requests that can delete arbitrary files and read sensitive files on the server. The attack executes with NT AUTHORITY/SYSTEM privileges, giving the attacker full control over the affected Windows host.
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= 13CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Applications Manager installationLocate the ManageEngine Applications Manager installation directory. On Windows, common paths include C:\ManageEngine\ApplicationsManager or C:\Program Files\ManageEngine\ApplicationsManager. Check for the presence of run.bat, start.bat, or the main executable.Affected if Applications Manager is installed on the system
-
Check installed build versionOpen the file 'buildnum.txt' in the Applications Manager installation directory, or access the product's 'About' page in the admin console. Compare the build number to 13740.Affected if Build number is less than 13740 (e.g., 13690, 13600, etc.)
-
Identify if CustomFieldsFeedServlet is exposedCheck network accessibility of the endpoint /feed/CustomFieldsFeedServlet. This can be done by reviewing web server configuration files in the conf directory or attempting a local HTTP request to http://localhost:8080/feed/CustomFieldsFeedServlet (adjust port if different).Affected if The servlet endpoint is reachable and responds to requests
-
Verify Windows platform and service contextConfirm the operating system is Windows. Check the service configuration in Windows Services (services.msc) to see if Applications Manager runs under NT AUTHORITY/SYSTEM or another high-privilege account.Affected if Applications Manager runs on Windows as NT AUTHORITY/SYSTEM service
The environment is affected if Zoho ManageEngine Applications Manager version 13 is installed with a build number below 13740 on a Windows host where the CustomFieldsFeedServlet endpoint is accessible.
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 · scopedApply the vendor patch by upgrading to Applications Manager build 13740 or later. If immediate patching is not possible, restrict network access to the affected servlet endpoint and monitor for suspicious file access patterns.
Applications Manager Version 13 build 13740 or later
- 1. Log in to the ManageEngine Applications Manager administrative console.
- 2. Navigate to the 'Help' or 'About' section to verify the current build number.
- 3. If the build number is below 13740, initiate the upgrade process.
- 4. Download the latest build (13740 or later) from the official ManageEngine support portal at www.manageengine.com.
- 5. Back up the current Applications Manager installation and database before proceeding with the upgrade.
- 6. Run the upgrade installer and follow the on-screen prompts to complete the update.
- 7. After installation, verify the build number has been updated to 13740 or higher.
- 8. Test that the CustomFieldsFeedServlet functionality is working correctly after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11808 — 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-2018-11808 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