npm package report

Is @nocobase/plugin-notification-in-app-message safe?

1 known vulnerability, worst severity CRITICAL.

cvss
10.0

how bad it is if exploited, out of 10

epss
0.90%

chance of exploitation in the next 30 days

xyz score
4.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-p849-8hwh-84j9, the advisory selected below

// advisories

GHSA-p849-8hwh-84j9

CRITICALCVE-2026-52887

GET /api/myInAppChannels:list accepts a structured filter query parameter. The handler for the latestMsgReceiveTimestamp field splices the $lt value directly into a Sequelize.literal() template string with no escape, type cast, or parameter binding. The action ACL is loggedIn, so any authenticated account reaches it. The default auth-basic authenticator ships allowSignUp: true, so the account is o

Affected
<= 2.0.60
Fixed in
2.0.61
Weakness
CWE-89
Published
2026-07-31
Source
github

GHSANVDMITREreferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:54 UTC. The most recent advisory here was published 2026-07-31. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @nocobase/plugin-notification-in-app-message safe? npm package security report | CyberXYZ