dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-52887

CRITICAL · 10.0 CVSS v3.1 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 5 weeks old

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
NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to 2.0.61, NocoBase @nocobase/plugin-notification-in-app-message exposed GET /api/myInAppChannels:list, where the filter[latestMsgReceiveTimestamp][$lt] value was inserted into a Sequelize.literal() template string without escaping or parameter binding, allowing a signed-up authenticated user to run stacked PostgreSQL statements and potentially execute commands with COPY ... TO PROGRAM. This vulnerability is fixed in 2.0.61.

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 in NocoBase's @nocobase/plugin-notification-in-app-message allows authenticated users to inject malicious SQL via the filter[latestMsgReceiveTimestamp][$lt] parameter passed to Sequelize.literal() without parameter binding. This enables stacked PostgreSQL queries and potentially OS command execution through the COPY TO PROGRAM feature.

MitigationUpgrade NocoBase to version 2.0.61 or later to apply the fix. Alternatively, disable the notification-in-app-message plugin if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 if the in-app notification plugin is installed
    Check your NocoBase plugins directory or configuration file for @nocobase/plugin-notification-in-app-message. In a typical installation, inspect the package.json dependencies or the storage/core/plugins database table for this plugin name.
    Affected if The plugin @nocobase/plugin-notification-in-app-message is present and enabled in the application
  2. Determine the installed NocoBase version
    Run the command 'npm list @nocobase/server' or check the version field in your package.json file, or query the application's API endpoint that returns version information if available.
    Affected if The NocoBase version is earlier than 2.0.61 (the fixed release)
  3. Verify the database type in use
    Inspect your NocoBase configuration file (typically config/database.ts or .env) for the DB_DIALECT or similar database connection setting, or query the database type from the application configuration.
    Affected if PostgreSQL is the underlying database, which enables the COPY TO PROGRAM command execution vector described in the CVE
  4. Check for recent SQL injection attempts in logs
    Review application logs, database logs, or security audit logs for patterns containing 'latestMsgReceiveTimestamp' combined with unusual SQL operators, stacked queries, or PostgreSQL system commands.
    Affected if Log entries show the filter[latestMsgReceiveTimestamp][$lt] parameter being used with suspicious SQL content or unexpected operators

You are affected if the @nocobase/plugin-notification-in-app-message plugin is enabled, your NocoBase version is below 2.0.61, and you are using PostgreSQL as your database backend.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade NocoBase to version 2.0.61 or later to apply the fix. Alternatively, disable the notification-in-app-message plugin if not required.

Recommended fix High confidence

NocoBase 2.0.61

  1. Identify the current NocoBase version in use by checking the package.json or installation
  2. Upgrade NocoBase to version 2.0.61 or later by running the appropriate package manager command (e.g., npm update @nocobase/server or equivalent)
  3. If using a containerized deployment, update the Docker image tag to use version 2.0.61 or later
  4. After upgrading, verify the /api/myInAppChannels:list endpoint no longer uses Sequelize.literal() with unsanitized filter parameters by reviewing the plugin code or release notes
  5. Test the upgraded system to ensure the notification in-app message functionality still works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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