CVE-2023-48646
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 · uneditedZoho ManageEngine RecoveryManager Plus before 6070 allows admin users to execute arbitrary commands via proxy 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 confidenceZoho ManageEngine RecoveryManager Plus versions before 6070 contain a vulnerability allowing authenticated administrator users to execute arbitrary operating system commands through the application's proxy settings interface. This represents a privilege escalation and remote code execution vulnerability accessible to users with administrative access.
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< 6.0= 6.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate RecoveryManager Plus installationSearch for the RecoveryManager Plus installation directory, typically found in C:\Program Files\ManageEngine\RecoveryManager Plus or /opt/ManageEngine/RecoveryManager Plus on Linux. Check for the main executable file (RecoveryManagerPlus.exe or start.sh).Affected if RecoveryManager Plus is installed on the system
-
Identify installed versionCheck the version of the installed RecoveryManager Plus. In the installation directory, look for a version info file, or access the application web interface and check the About/Version page typically found at https://localhost:8090 or the configured port.Affected if The installed version is less than 6070 (versions 6.0 and below, or any build below 6070)
-
Verify administrative access existsCheck if there are any administrator-level user accounts configured in RecoveryManager Plus. Access the Admin/Settings > User Management section in the web interface to list administrative users.Affected if At least one administrator user account is configured with access to proxy settings
-
Confirm proxy settings feature is accessibleNavigate to the proxy settings interface in the RecoveryManager Plus web console, typically under Settings > General Settings > Proxy Configuration. Verify this feature is available and modifiable by admin users.Affected if Proxy settings interface is accessible and modifiable by the current admin user
The environment is affected if Zoho ManageEngine RecoveryManager Plus is installed with a version below 6070 and the proxy settings feature is accessible to administrator users.
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 · scoped6.0
Upgrade Zoho ManageEngine RecoveryManager Plus to version 6070 or later. Implement strict administrative access controls and audit logging for proxy configuration changes.
Version 6070 or later (build 6070)
- 1. Identify the current version of RecoveryManager Plus by accessing the About section in the admin console
- 2. If version is below 6070, plan for upgrade during a maintenance window
- 3. Back up the RecoveryManager Plus database and configuration files
- 4. Download RecoveryManager Plus version 6070 or later from the official ManageEngine download page
- 5. Stop the RecoveryManager Plus service before upgrading
- 6. Run the installer and follow the on-screen upgrade instructions
- 7. Start the RecoveryManager Plus service after upgrade completes
- 8. Verify the upgrade was successful by checking the version number in the About section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48646 — 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-2023-48646 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