NocoBase SQL Injection via Unprotected Collection Update

NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.39, the checkSQL() validation function that blocks dangerous SQL keywords (e.g., pg_read_file, LOAD_FILE, dblink) is applied on the collections:create and sqlCollection:execute endpoints but is entirely missing on the sqlCollection:update endpoint. An attacker with collection management permissions can create a SQL collection with benign SQL, then update it with arbitrary SQL that bypasses all validation, and query the collection to execute the injected SQL and exfiltrate data. This issue has been patched in version 2.0.39.

Casky was already ahead

This CVE exploits attack patterns that Casky's 301matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

NocoBase versions prior to 2.0.39 contain a critical SQL injection vulnerability where the checkSQL() validation function—designed to block dangerous SQL keywords like pg_read_file, LOAD_FILE, and dblink—is inconsistently applied across endpoints. While the collections:create and sqlCollection:execute endpoints implement this protection, the sqlCollection:update endpoint entirely lacks validation. This creates a bypass mechanism where attackers with collection management permissions can create benign SQL collections that pass initial validation, then update them with malicious SQL payloads to achieve unauthorized data access or database compromise. Organizations running affected NocoBase versions face risk of data exfiltration, privilege escalation, and complete database takeover depending on database credentials and permissions.

Casky's 301 mapped security skills—leveraging Claude's extended reasoning across MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance)—detect this attack pattern by correlating CWE-89 (SQL Injection) and CWE-284 (Improper Access Control) indicators. Practitioners using Casky would observe findings flagging: (1) inconsistent input validation patterns across API endpoints in application logs, specifically collection creation requests followed by suspicious update operations with SQL keywords; (2) role-based access anomalies where low-privilege users execute sqlCollection:update calls; and (3) database query logs showing execution of dangerous functions (pg_read_file, LOAD_FILE) originating from NocoBase application contexts. The platform's skill mapping enables practitioners to rapidly pivot from vulnerability indicators to defensive posture improvements across endpoint hardening and access control validation.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

301 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-41641.

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-campaign-attribution-evidence

threat intelligence · low

Run

analyzing-certificate-transparency-for-phishing

threat intelligence · low

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-41641

Casky has 301 skills that investigate the attack patterns behind CVE-2026-41641. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn