CVE-2025-58634 is a security vulnerability classified under CWE-862, which pertains to Missing Authorization in the PeachPay Payments plugin. This vulnerability arises due to incorrectly configured access control mechanisms within the PeachPay Payments system, allowing unauthorized users to perform actions that should require proper authorization. The affected product versions include PeachPay Payments up to version 1.117.4, with no specific lower bound version indicated. The vulnerability has a CVSS 3.1 base score of 5.3, indicating a medium severity level. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) reveals that the vulnerability can be exploited remotely over the network without any privileges or user interaction, and it does not affect confidentiality or availability but impacts integrity. Specifically, the vulnerability allows an attacker to alter or manipulate data or transactions within the payment system without proper authorization, potentially leading to fraudulent payment processing or manipulation of payment records. Although no known exploits are reported in the wild at this time, the nature of the vulnerability suggests that it could be leveraged by attackers to bypass access controls and perform unauthorized operations. The lack of patch links indicates that a fix may not yet be publicly available, emphasizing the need for vigilance and mitigation by affected organizations.

For European organizations using PeachPay Payments, this vulnerability poses a risk to the integrity of payment processing systems. Unauthorized manipulation of payment data could lead to financial discrepancies, fraud, and loss of trust from customers and partners. Given the critical role of payment systems in e-commerce and retail sectors, exploitation could disrupt business operations and result in regulatory scrutiny under frameworks such as GDPR if personal or transactional data integrity is compromised. Additionally, financial institutions or merchants relying on PeachPay Payments may face reputational damage and potential financial losses. The fact that exploitation requires no privileges or user interaction increases the risk profile, as attackers can remotely target vulnerable systems without needing to compromise user credentials. However, since confidentiality and availability are not impacted, the threat is primarily focused on data integrity and transactional correctness. This could lead to unauthorized changes in payment amounts, transaction statuses, or other critical payment-related data, which may have downstream effects on accounting and compliance.

European organizations should immediately audit their use of PeachPay Payments to determine if they are running affected versions (up to 1.117.4). Until an official patch is released, organizations should implement strict network-level access controls to limit exposure of the payment system interfaces to trusted IP addresses only. Employing Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized access attempts targeting PeachPay endpoints can help mitigate exploitation risks. Monitoring and logging all payment-related transactions for anomalies or unauthorized changes is critical to detect potential exploitation early. Organizations should also review and tighten internal access control policies and configurations within PeachPay Payments to ensure that authorization checks are correctly enforced. Engaging with the vendor or security community for updates on patches or workarounds is essential. Finally, integrating multi-factor authentication and least privilege principles for administrative access to payment systems can reduce the risk of unauthorized changes.