Security readout for executives and security teams
Plain-English summary
A critical SQL injection flaw is reported in mfish-nocode-pro v1.0.0. An unauthenticated remote attacker could manipulate the tableName input to access sensitive database information. The supplied CVSS assessment also indicates possible data modification and service disruption, creating potentially severe confidentiality, integrity, and availability consequences.
Executive priority
Treat as an immediate investigation and containment priority wherever mfish-nocode-pro v1.0.0 may be deployed. Prioritize externally reachable instances and systems connected to sensitive databases. Because no fix is named in the supplied sources, owners should seek current project guidance and document interim access restrictions.
Technical view
CVE-2026-79570 is classified as CWE-89 at /sys/dbConnect/data, where the tableName parameter reportedly accepts crafted SQL. CVSS 3.1 scores it 9.8: network-accessible, low complexity, no privileges or user interaction required, with high confidentiality, integrity, and availability impacts. The bundle does not identify a patched version.
Likely exposure
Highest risk applies to Internet-accessible mfish-nocode-pro v1.0.0 deployments exposing /sys/dbConnect/data. Internal deployments may remain reachable by compromised users or systems. The CVE metadata lists affected vendor, product, and versions as “n/a,” so asset identification requires confirming application names, versions, routes, and deployment records locally.
Exploitation context
A public technical reference is listed, but the supplied evidence does not establish active exploitation. The CVE is not identified as being in KEV. Its unauthenticated network attack vector and low reported complexity make exposed instances urgent to investigate, without proving that attacks are occurring.
Researcher notes
The report identifies a parameter and endpoint but the structured affected-product fields are incomplete, with vendor, product, and versions recorded as “n/a.” CVSS predicts full confidentiality, integrity, and availability impact, while the description explicitly mentions sensitive-information access. Confirm broader impact during authorized validation; do not infer exploitation or patch availability from the score alone.
Mitigation direction
- Check the project or vendor guidance immediately for an official fix or supported upgrade.
- Restrict external access to /sys/dbConnect/data until remediation is confirmed.
- Apply least-privilege database permissions to limit potential impact.
- Monitor requests and database activity for suspicious manipulation of tableName.
- Use compensating request filtering only as temporary containment, not a permanent fix.
Validation and detection
- Inventory mfish-nocode-pro deployments and confirm whether version 1.0.0 is present.
- Determine whether /sys/dbConnect/data is reachable without authentication from untrusted networks.
- Review application and database logs for anomalous tableName values or unexpected queries.
- Verify database credentials have only the permissions required by the application.
- After remediation, confirm the endpoint safely rejects malformed tableName input in an authorized test environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-79570 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fangtang7/CVE/blob/main/mfish-nocode/sql.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.