Yu-Hsiang Huang

This issue could lead to denial-of-service or service crashes. Exploitation of the `moxa cmd` service, due to insufficient input validation, allows attackers to disrupt operations. If exposed to public networks, the issue poses a significant remote threat, potentially allowing attackers to shut down affected systems.

A stored Cross-site Scripting (XSS) issue was found. The `username` parameter of the "/install/index.php" page is vulnerable. This can be demonstrated via the "admin/login.php" page.

A reflected Cross-site Scripting (XSS) issue was found. The issue is related to the "method" parameter of the "data/api/oauth/connect.php" page.

The issue allows for Cross-site request forgery (CSRF) that can be used to delete a database. This can be achieved via the "/?q=wrkfrm&type=databases" API endpoint.

The issue allows session fixation via the `sessid` parameter in the "data.php" endpoint.

The issue allows for XSS via the `data.php` task parameter in the ` includesonline.php` file, but only if the ` users/admin/tasks.php` file exists.

The issue allows for remote code execution (RCE) after an attacker writes shell code into the database and executes the Backup Database function with a .php filename for the backup's archive file.

A Stored Cross-site Scripting (XSS) issue was found in the Add User function of the User Manager pages, specifically in the `User Name` field.

The issue is related to a reflected Cross-site Scripting (XSS) vulnerability. This occurs in the `content1` parameter of the php/demo.php endpoint.

The issue is related to a Stored Cross-site Scripting (XSS) vulnerability. This vulnerability is found in the Add Host function of the Manage Hosts pages, specifically in the `User Name` field.

A reflected Cross-site Scripting (XSS) issue was found. The `dbs` parameter of the 'conn.php' page is vulnerable.

An issue was discovered where the database name is not strictly filtered, allowing an attacker to insert a name containing an XSS Payload, leading to stored XSS.

An issue was discovered in the software, where the `userid` parameter in the "jumpin.php" endpoint has a SQL injection issue.

A SQL injection attack can be triggered through the designer feature by using a specially crafted `username`. This allows for potential exploitation.

The issue is related to Incorrect Access Control in the Z CreateCompanyTemplateFile.php file, allowing the overwrite of an existing .sql file on the target web site. This can be achieved by creating a template and then using ../ directory traversal in the `TemplateName` parameter.

A Cross-Site Scripting (XSS) issue was found in the navigation tree, allowing an attacker to deliver a payload to a user through a crafted database or table name.

The issue is related to insufficient protection of the web page structure in the index.php component of the PHP-Proxy web proxy script, allowing a remote attacker to perform cross-site scripting (XSS) attacks via the URL field in index.php.

An issue was discovered in the Manufacturing component. It has Blind SQL Injection via the `SearchParts` parameter in CollectiveWorkOrderCost.php.

An issue was discovered in the Sales component. The SalesInquiry.php file has SQL Injection via the `SortBy` parameter.

An issue was discovered on the Bank Account Matching - Receipts screen of the General Ledger component. This issue involves Blind SQL injection via the `AmtClear ` parameter in BankMatching.php.