CVE-2023-46157
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 · uneditedFile-Manager in MGT CloudPanel 2.0.0 through 2.3.2 allows the lowest privilege user to achieve OS command injection by changing file ownership and changing file permissions to 4755.
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 confidenceThe File-Manager component in MGT CloudPanel versions 2.0.0 through 2.3.2 contains a privilege escalation vulnerability allowing the lowest-privileged users to achieve OS command injection. Attackers exploit this by manipulating file ownership and setting file permissions to 4755 (setuid), which enables execution of commands with elevated privileges.
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>= 2.0.0, <= 2.3.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify MGT CloudPanel versionLocate the installed CloudPanel version by checking the package manager, control panel about page, or version file in the CloudPanel installation directoryAffected if The installed version falls within the range 2.0.0 to 2.3.2 inclusive
-
Verify File-Manager component accessConfirm whether the File-Manager functionality is enabled and accessible to user accounts, particularly to users with the lowest privilege levelAffected if File-Manager is enabled and low-privilege users have access to it
-
Scan for setuid files with 4755 permissionsSearch the filesystem for files with permission mode 4755 (setuid), particularly in user-accessible directories such as web document roots, /tmp, or user home directoriesAffected if Unexpected files with 4755 permissions exist, especially in locations writable by low-privilege users
-
Audit recent file ownership changesReview system logs or audit files for recent changes to file ownership, particularly ownership transfers to low-privilege users on executable filesAffected if Recent file ownership changes to executables are present that were not initiated by administrators
A user is affected if they have MGT CloudPanel versions 2.0.0-2.3.2 running with File-Manager enabled and accessible to low-privilege 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 · scopedUpgrade MGT CloudPanel to version 2.3.3 or later. If immediate patching is not possible, restrict or disable the File-Manager functionality for low-privilege users as a temporary compensating control.
A version newer than 2.3.2 (consult official CloudPanel release notes for the first fixed release)
- 1. Identify the currently installed CloudPanel version using the admin interface or command line
- 2. Backup all critical data and configuration files before performing any upgrade
- 3. Consult the official CloudPanel release notes at www.cloudpanel.io for the fixed version after 2.3.2
- 4. Follow the official upgrade documentation to update to the latest stable release
- 5. Verify the File-Manager component is updated and test that file ownership/permission changes no longer allow command injection
- 6. Confirm the upgrade was successful and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46157 — 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-46157 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