Description

Weak Password Recovery Mechanism for Forgotten Password vulnerability in AKIN Software Computer Import-Export Industry and Trade Co. Ltd. MyRezzta allows Password Recovery Exploitation. This issue affects MyRezzta: from 2.06.03 before 2.07.01.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.1",
  "pubDate": "2026-10-08T13:17:16.753Z",
  "pubdate": "2026-10-08T13:17:16.753Z",
  "executiveSummary": "A security vulnerability has been identified in AKIN Software Computer Import-Export Industry and Trade Co. Ltd. MyRezzta, specifically concerning its password recovery mechanism. This vulnerability affects MyRezzta versions from 2.06.03 up to (but not including) 2.07.01. The weakness lies in the implementation of the 'forgotten password' functionality, which permits password recovery exploitation.\nAn unauthorized remote attacker could exploit this flaw to bypass authentication controls and compromise user accounts. Depending on the privileges associated with the targeted account, successful exploitation could lead to unauthorized access to sensitive application data, administrative interfaces, and underlying system configurations.\nThis vulnerability poses a significant risk to organizational confidentiality and integrity, as it allows attackers to gain persistent access without possessing valid credentials prior to the attack. No complex exploitation requirements or prior authentication are necessary to initiate the recovery process, making this a high-priority issue for remediation. Organizations running affected versions of MyRezzta should immediately assess their deployments and apply necessary updates or defensive configurations to mitigate the risk of account takeover.",
  "technicalDetails": "The root cause of this vulnerability lies in the weak design of the password recovery workflow within the MyRezzta application (versions 2.06.03 through 2.06.xx/2.07.00). In a secure password recovery implementation, the system must generate a cryptographically secure, random, and single-use token associated with a specific user account, expiring after a short duration. The vulnerability in MyRezzta indicates a failure to adhere to these secure design principles.\nThe exploitation mechanism typically involves predicting, brute-forcing, or bypassing the validation steps of the recovery token or identifier. This can occur if the application relies on predictable recovery tokens (such as sequential IDs, timestamps, or weakly hashed user identifiers) or fails to implement sufficient entropy in token generation. Additionally, the recovery mechanism may lack robust rate-limiting controls, enabling remote attackers to perform automated brute-force attacks against the recovery endpoint.\nThe attack flow begins with the threat actor identifying a target user account (e.g., an administrator or high-privilege user email or username). The attacker initiates the 'forgotten password' request via the MyRezzta web interface. The application generates a password reset link or token. If the token generation is predictable, the attacker intercepts or generates the matching token offline or online.\nOnce the validation check is bypassed, the application processes the password change request, allowing the attacker to define a new password for the target account. Because the vulnerability requires no prior authentication and can be conducted entirely over the network, it presents a low barrier to entry for external actors. The post-exploitation impact is severe, as gaining unauthorized access to a MyRezzta account can allow the attacker to manipulate database records, view confidential transaction or business data, and potentially pivot to gain broader access within the hosting network infrastructure."
}