CVE-2024-55963
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 · uneditedAn issue was discovered in Appsmith before 1.51. A user on Appsmith that doesn't have admin permissions can trigger the restart API on Appsmith, causing a server restart. This is still within the Appsmith container, and the impact is limited to Appsmith's own server only, but there is a denial of service because it can be continually restarted. This is due to incorrect access control checks, which should check for super user permissions on the incoming request.
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 confidenceAppsmith before version 1.51 has an authorization bypass where non-admin users can trigger the server restart API. The endpoint incorrectly validates permissions, failing to check for super user status before allowing the restart action, leading to denial of service through repeated container restarts.
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< 1.51CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Determine installed Appsmith versionLocate the current Appsmith version number. This is typically displayed in the Appsmith UI footer, accessible via the Admin Settings About page, or can be retrieved using the Appsmith CLI tool (appsmithctl --version) or by inspecting the deployment configuration.Affected if The installed version is any release before 1.51 (for example, 1.50, 1.49, 1.48, etc.)
-
Identify if non-admin users can access restart APIReview the API access control configuration or audit logs for the server restart endpoint. Check whether the system enforces super user role verification before allowing restart operations, or if it incorrectly permits admin-level users without super admin privileges.Affected if The restart API endpoint accepts and processes requests from authenticated users who lack super user status, or the endpoint lacks proper permission validation for the super admin role
-
Check for super user role configurationExamine the user management system to determine whether a distinct super admin role exists and whether it is required for server restart operations. Verify if the permission model distinguishes between regular admin and super admin privileges.Affected if The system does not implement a separate super user role requirement, or the restart endpoint ignores super user validation
The environment is affected if Appsmith version is below 1.51 AND the server restart API endpoint can be accessed by users who are not designated as super admins.
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 · scoped1.51
Upgrade to Appsmith 1.51 or later which implements proper super user permission validation for the restart API endpoint.
Appsmith 1.51
- Upgrade Appsmith to version 1.51 or later to receive the security fix for improper access control on the restart API
- After upgrading, verify that only users with super user permissions can access the restart API endpoint
- Confirm the server restart functionality now properly enforces access control checks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55963 — 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-2024-55963 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