dbcve.org
Manageengine OpmanagerApplication · Zohocorp

CVE-2018-18949

CRITICAL · 9.8 CVSS v3.0 Published 2018-11-05
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 OpManager 12.3 before 123222 has SQL Injection via Mail Server settings.

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

SQL injection vulnerability in Zoho ManageEngine OpManager 12.3 before build 123222 allows remote attackers to inject malicious SQL queries through the Mail Server settings interface. The lack of proper input sanitization on mail server configuration parameters enables authenticated attackers (or potentially unauthenticated if mail server settings are accessible) to execute arbitrary SQL commands against the backend database.

MitigationUpgrade Zoho ManageEngine OpManager to version 12.3 build 123222 or later to obtain the patched version. If immediate upgrade is not possible, restrict network access to the OpManager admin interface and disable mail server configuration features until the patch can be applied.

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 OpmanagerApplication
Affected:= 11.4= 11.5= 12.3

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.0/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 OpManager version
    Log into the OpManager web interface and navigate to the About or Settings page to view the product version number, or check the version file in the OpManager installation directory
    Affected if The installed version is 11.4, 11.5, or 12.3 (any build before 123222)
  2. Check build number for version 12.3
    If running OpManager 12.3, locate the build number in the About page or version details; build numbers are typically displayed as a numeric value
    Affected if Running OpManager 12.3 with build number less than 123222
  3. Verify mail server settings accessibility
    Navigate to the Mail Server configuration section within OpManager settings (typically under Admin or Settings > Mail Server Settings)
    Affected if The mail server settings interface is accessible without restriction, as this is the attack vector for the SQL injection

You are affected if your OpManager installation is version 11.4, 11.5, or version 12.3 with build lower than 123222, and the mail server settings feature is accessible in your deployment

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

Upgrade Zoho ManageEngine OpManager to version 12.3 build 123222 or later to obtain the patched version. If immediate upgrade is not possible, restrict network access to the OpManager admin interface and disable mail server configuration features until the patch can be applied.

Recommended fix Moderate confidence

OpManager 12.3 build 123222 or later

  1. 1. Back up your OpManager database and configuration files before proceeding with any upgrade.
  2. 2. Download OpManager version 12.3 build 123222 or later from the official ManageEngine download page (www.manageengine.com).
  3. 3. Stop the OpManager service before upgrading.
  4. 4. Run the installer for the new version, following the on-screen prompts.
  5. 5. After installation, start the OpManager service and verify the Mail Server settings are accessible.
  6. 6. Verify the SQL injection vulnerability is resolved by confirming the Mail Server settings function correctly without errors.
  7. 7. Review release notes for any additional post-upgrade configuration requirements.
Caveat Standard upgrade precautions apply - backup data before upgrading, test in non-production environment first

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

Fix this in Manageengine Opmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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