dbcve.org
AppsmithApplication

CVE-2024-55965

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-26
Fix available
A fix is available. Upgrade to 1.51 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An issue was discovered in Appsmith before 1.51. Users invited as "App Viewer" incorrectly have access to development information of a workspace (specifically, a list of datasources in a workspace they're a member of). This information disclosure does not expose sensitive data in the datasources, such as database passwords and API Keys.

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

In Appsmith before version 1.51, the 'App Viewer' role incorrectly had authorization to list datasources within workspaces they were members of. This is a broken access control issue where the App Viewer role (intended for read-only access to published applications) was granted unintended visibility into development-level workspace information.

MitigationUpgrade Appsmith to version 1.51 or later to receive the access control fix that properly restricts App Viewer role permissions.

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
AppsmithApplication
Affected:< 1.51

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Appsmith version
    Check the Appsmith instance version through the admin settings, About page, or by querying the system metadata (typically accessible via the platform's version endpoint or admin console)
    Affected if The installed version is any version before 1.51 (e.g., 1.50, 1.49, etc.)
  2. Identify App Viewer role users
    Review user management or access control settings to enumerate users assigned the App Viewer role within workspaces
    Affected if Any users are assigned the App Viewer role in the system
  3. Verify App Viewer can list datasources
    Using a test account with App Viewer role, attempt to access the datasource listing endpoint within a workspace the user is a member of
    Affected if The App Viewer role user can successfully retrieve or list datasource information within their workspace
  4. Review datasource access logs
    Inspect Appsmith audit logs, access logs, or security event logs for datasource listing operations performed by users with App Viewer role
    Affected if Logs show datasource list/get operations originating from App Viewer role accounts

The environment is affected if running any Appsmith version below 1.51 AND the App Viewer role is active in the system, since the broken access control allows unintended datasource visibility.

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
Upgrade available Upgrade to 1.51 or later
Fixed in 1.51
Interim mitigation

Upgrade Appsmith to version 1.51 or later to receive the access control fix that properly restricts App Viewer role permissions.

Recommended fix High confidence

Appsmith 1.51

  1. 1. Back up your current Appsmith instance and database before upgrading.
  2. 2. Review the Appsmith 1.51 release notes for any migration requirements or breaking changes.
  3. 3. Upgrade your Appsmith instance to version 1.51 or later.
  4. 4. After upgrade, verify that 'App Viewer' role users can no longer access the datasource list in the workspace.
  5. 5. Confirm that the authorization controls are working correctly for all user roles.
Caveat Review Appsmith 1.51 release notes for any breaking changes before upgrading

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

Fix this in Appsmith Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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