CVE-2026-6562
SQL Injection in dameng100 muucmf getListByPage Function
Publication date: 2026-04-19
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dameng | muucmf | 1.9.5.20260309 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| 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 Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a flaw found in dameng100 muucmf version 1.9.5.20260309, specifically in the function getListByPage within the file /index/Search/index.html.
The issue arises from improper handling of the argument 'keyword', which can be manipulated to perform an SQL injection attack.
This means an attacker can remotely execute malicious SQL commands on the database by exploiting this flaw.
The exploit for this vulnerability has been published and is available for use.
The vendor was informed early about this issue but did not respond.
How can this vulnerability impact me? :
This vulnerability allows an attacker to remotely perform SQL injection attacks on the affected system.
Such attacks can lead to unauthorized access to sensitive data, data modification, or even deletion.
Because the attack can be performed without any privileges or user interaction, it poses a significant security risk.
The published exploit increases the likelihood of exploitation by malicious actors.