CVE-2026-79570
Deferred Deferred - Pending Action

SQL Injection in mfish-nocode-pro Application

Vulnerability report for CVE-2026-79570, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-08

Last updated on: 2026-09-09

Assigner: MITRE

Description

mfish-nocode-pro v1.0.0 was discovered to contain a SQL injection vulnerability in the tableName parameter at /sys/dbConnect/data. This vulnerability allows attackers to access sensitive database information via a crafted SQL statement.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-08
Last Modified
2026-09-09
Generated
2026-09-29
AI Q&A
2026-09-10
EPSS Evaluated
2026-09-27
NVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a SQL injection vulnerability in mfish-nocode-pro v1.0.0 affecting the /sys/dbConnect/data endpoint. The tableSchema parameter is passed unfiltered into a MySQL query without validation, allowing attackers to inject malicious SQL statements. The tableName parameter is validated but tableSchema is not, enabling exploitation.

Detection Guidance

To detect this SQL injection vulnerability, monitor network traffic for requests to the /sys/dbConnect/data endpoint with suspicious tableSchema parameters. Check application logs for error-based SQL injection patterns like extractvalue() or database version leaks. Use tools like SQLmap to test for injection by sending crafted payloads to the parameter.

Impact Analysis

Attackers can access sensitive database information by injecting crafted SQL statements. They can retrieve data like current user, database name, or MySQL version through error messages. Exploitation requires a logged-in user with database connection access but bypasses permission checks.

Compliance Impact

This vulnerability could lead to unauthorized data access, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. It enables data breaches that may result in regulatory penalties and loss of compliance certifications.

Mitigation Strategies

Immediately update mfish-nocode-pro to a patched version if available. As a temporary fix, add input validation for the tableSchema parameter using a strict whitelist regex. Implement the @RequiresPermissions annotation to enforce sys:database:query permission checks on the endpoint. Disable error-based SQL injection by suppressing detailed database errors in responses.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-79570. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart