ThreatBeaconXSubscribe
Critical Broken Access Control · 7 min read

Critical WordPress CryptoPayment Gateway Vulnerability Allows Unauthenticated File Deletion and Wallet Credential Exposure

A critical security vulnerability, tracked as CVE-2026-81648, has been identified in the CryptoPayment Gateway WordPress plugin, affecting versions 1.2.1 and 1.2.2. The vulnerability originates from a missing authorization check in one of the plugin's AJAX endpoints. This weakness allows unauthenticated attackers to invoke sensitive administrative operations without requiring an account or an authenticated session. The exposed functionality includes reading and modifying payment gateway configurations, recovering stored cryptocurrency wallet credentials in cleartext, and deleting arbitrary files on the server. Security researcher Pedro Pinho published a proof of concept demonstrating how the vulnerability could be exploited. One demonstrated scenario involves deleting the WordPress wp-config.php file, potentially forcing the website into its initial configuration process. With a CVSS v3.1 score of 10.0, the vulnerability represents a critical risk to WordPress websites using the affected plugin, particularly those processing cryptocurrency payments or storing wallet-related credentials.

Written by Jakka Lakshmi Koumudi·Published Nov 3, 2026

Description

CryptoPayment Gateway is a WordPress plugin designed to support cryptocurrency payment functionality on websites.

CVE-2026-81648 affects versions 1.2.1 and 1.2.2 of the plugin.

The underlying security issue is a missing authorization check in an AJAX request handler. This allows unauthenticated users to access operations intended for administrative functionality.

The vulnerability can expose sensitive payment configuration information and stored wallet credentials. It also provides functionality that can be abused to delete arbitrary files within the server's filesystem, subject to the vulnerable handler's path construction and filesystem conditions.

The vulnerability was publicly disclosed in September 2026, with a verified proof of concept published by security researcher Pedro Pinho.

Technical Description

CVE-2026-81648 – Missing Authorization in CryptoPayment Gateway

  • Affected product: CryptoPayment Gateway WordPress plugin.

  • Affected versions: 1.2.1 to 1.2.2.

  • Vulnerability type: Missing Authorization.

  • CWE: CWE-862 – Missing Authorization.

  • CVSS v3.1: 10.0 – Critical.

  • Attack vector: Network.

  • Attack complexity: Low.

  • Privileges required: None.

  • User interaction: None.

  • Scope: Changed.

  • Confidentiality impact: High.

  • Integrity impact: High.

  • Availability impact: High.

The vulnerability exists because an AJAX endpoint processes administrative operations without properly verifying whether the requesting user has the required authorization.

The affected functionality includes:

  1. Retrieving payment gateway settings.

  2. Modifying payment gateway configuration.

  3. Decrypting stored wallet credentials.

  4. Deleting files through an inadequately validated file-deletion handler.

The vulnerable request handler accepts operations through a function parameter and executes the corresponding administrative functionality without enforcing the required access controls.

This creates an unauthenticated attack surface through which remote attackers can interact with sensitive plugin functionality.

Attack Overview

Based on the published proof of concept, the exploitation process can be summarized as follows:

  1. Target Identification: The attacker identifies a WordPress website running CryptoPayment Gateway version 1.2.1 or 1.2.2.

  2. Unauthenticated Endpoint Access: The attacker sends requests to the vulnerable plugin AJAX endpoint without providing an authenticated session.

  3. Configuration Disclosure: The attacker invokes the settings-retrieval functionality to access payment gateway configuration information.

  4. Configuration Manipulation: The attacker abuses the settings-update functionality to overwrite stored gateway configuration values.

  5. Credential Recovery: The attacker uses the plugin's decryption functionality to recover stored wallet credentials in cleartext.

  6. Arbitrary File Deletion: The attacker abuses the file-deletion functionality to remove files from the server.

  7. Potential Website Compromise: Deletion of critical WordPress configuration files can disrupt the website and potentially expose it to further compromise through the installation process.

The published proof of concept demonstrates these capabilities without requiring a WordPress account or authenticated session.

Technical Analysis

1. Missing Authorization Check

The primary weakness is located in the plugin's AJAX request-handling functionality.

The affected endpoint does not properly verify the authorization of incoming requests before processing sensitive operations.

In a secure implementation, administrative functionality should verify both authentication and the user's permissions before executing sensitive actions.

The absence of these checks allows external users to invoke functionality that should be restricted to authorized administrators.

2. Unauthorized Access to Payment Settings

The vulnerable handler exposes a function that retrieves the plugin's payment gateway settings.

An unauthenticated attacker can invoke this functionality and retrieve configuration information without logging into the WordPress administration panel.

This is particularly concerning because payment gateway configurations may contain sensitive business and wallet-related information.

3. Payment Configuration Manipulation

The plugin also exposes functionality that allows payment gateway settings to be modified.

The proof of concept demonstrates that an unauthenticated request can overwrite configuration values, including business information and cryptocurrency wallet-related settings.

If abused, this functionality could undermine payment integrity and potentially redirect payment-related information or transactions, depending on the configuration and how the website processes payments.

4. Cryptocurrency Wallet Credential Exposure

One of the most serious aspects of this vulnerability is the ability to recover stored wallet credentials.

The plugin includes a decryption operation that can be invoked through the same vulnerable request handler.

The published proof of concept demonstrates how encrypted wallet credential material can be passed to this functionality and returned in cleartext.

This could expose sensitive cryptocurrency wallet information and create financial risks for organizations relying on the affected payment gateway.

The actual financial impact would depend on the privileges and usability of the recovered wallet credentials.

5. Arbitrary File Deletion

The vulnerability also affects the plugin's file-deletion functionality.

The affected handler constructs a filesystem path using a filename supplied by the requester without adequately sanitizing or validating the path.

This creates a path traversal risk that can allow attackers to target files outside the intended directory.

The proof of concept demonstrates how an attacker can first create the required directory through an upload operation and subsequently abuse the deletion handler to remove the WordPress wp-config.php file.

The wp-config.php file contains important WordPress configuration information, including database connection details.

Removing this file can disrupt the website and cause WordPress to redirect visitors to its initial configuration process.

This creates an opportunity for further compromise if the database and hosting environment permit an attacker to complete the installation process.

6. Public Proof of Concept

Security researcher Pedro Pinho published a verified proof of concept demonstrating the vulnerability.

The demonstrated functionality includes:

  • Unauthenticated payment settings retrieval.

  • Unauthorized payment configuration modification.

  • Recovery of stored wallet credentials.

  • Arbitrary file deletion.

  • Potential disruption of the WordPress installation process.

The proof of concept confirms that the vulnerability is not merely theoretical.

However, the existence of a verified proof of concept does not establish that every vulnerable website has been exploited in the wild.

Potential Impact

Successful exploitation of CVE-2026-81648 could have serious consequences for websites using the affected plugin.

  • Cryptocurrency Wallet Exposure: Attackers may recover stored wallet credentials in cleartext, potentially creating financial risks.

  • Payment Configuration Manipulation: Unauthorized modifications could affect payment gateway settings and transaction handling.

  • Website Disruption: Deletion of critical files may interrupt website functionality.

  • Potential Website Takeover: Manipulation of WordPress installation files may create opportunities for further compromise.

  • Sensitive Information Exposure: Unauthorized access to payment configuration data may expose business and operational information.

  • Data Integrity Risks: Attackers may alter payment-related settings or remove important website files.

The combination of credential exposure, configuration manipulation and arbitrary file deletion makes this vulnerability particularly serious for websites processing cryptocurrency payments.

Recommendations

Immediate Actions

  1. Identify WordPress websites running CryptoPayment Gateway versions 1.2.1 or 1.2.2.

  2. Disable or remove the affected plugin until a verified security fix is available.

  3. Restrict public access to the affected plugin's AJAX functionality where possible.

  4. Review web server and WordPress logs for unexpected requests to the vulnerable AJAX handler.

  5. Investigate unauthorized payment gateway configuration changes.

  6. Check for unexpected file deletion, especially involving wp-config.php.

  7. If wallet credentials may have been exposed, move funds to a newly secured wallet and rotate affected credentials using a trusted process.

  8. Review WordPress administrator accounts, database activity and website configuration for signs of compromise.

  9. Preserve relevant logs and forensic evidence if exploitation is suspected.

Preventive Measures

  1. Keep WordPress core, plugins and themes updated.

  2. Install plugins only from trusted and verified sources.

  3. Enforce authentication and capability checks for all administrative AJAX operations.

  4. Apply strict input validation and path sanitization to file-handling functionality.

  5. Protect sensitive cryptocurrency credentials using appropriate encryption and access controls.

  6. Avoid storing wallet private keys in application configurations unless absolutely necessary.

  7. Use a Web Application Firewall (WAF) to help detect suspicious requests to plugin endpoints.

  8. Implement file integrity monitoring to identify unauthorized changes to important WordPress files.

  9. Maintain regular, offline or isolated backups and test website recovery procedures.

  10. Monitor payment gateway configuration changes and unexpected administrative operations.

Conclusion

CVE-2026-81648 demonstrates how a missing authorization check in a WordPress plugin can expose critical administrative functionality to unauthenticated attackers.

The vulnerability is especially concerning because it combines multiple security weaknesses within a single request-handling component, including unauthorized configuration access, wallet credential recovery and arbitrary file deletion.

For websites using cryptocurrency payment integrations, the exposure extends beyond ordinary website disruption and may introduce direct financial risks.

Organizations should immediately identify affected plugin installations, disable vulnerable versions until a verified fix is available, investigate suspicious activity and strengthen access controls around payment-related functionality.

This incident reinforces the importance of secure authorization checks, input validation and careful handling of sensitive financial credentials in third-party WordPress plugins.

Resources

1. https://www.vulncheck.com/blog/exploitation-targeting-node-red
2.https://cert-portal.siemens.com/productcert/html/ssa-834709.html

MITRE ATT&CK Mapping

T1212 – Exploitation for Credential Access