External risk intelligence

WordPress Payever WooCommerce Gateway Arbitrary File Upload Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-93754

The vulnerability affects a WooCommerce gateway plugin for WordPress. WordPress sites are typically deployed as public-facing web applications to facilitate e-commerce. The vulnerable callbacks are part of the web-accessible API surface, making them reachable over the public internet in standard deployments of this plugin.

Unrestricted File Upload

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the payever WooCommerce Gateway plugin, affecting its ability to securely handle file uploads. This flaw allows unauthenticated attackers to upload and execute arbitrary code on affected systems, potentially leading to a complete compromise of the web application. The main concern is to confirm if this plugin is in use and exposed to the internet.

  • Attackers can upload harmful files to websites.
  • Critical remote code execution risk discovered.
  • Confirm if your organization uses this plugin.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by accessing unauthenticated API callbacks on a WordPress site. These callbacks allow an attacker to upload a file, which the plugin then saves to the public uploads directory. By uploading a specially crafted file, an attacker can achieve remote code execution on the server.

  • No authentication needed to reach callbacks.
  • Uploading a malicious file triggers vulnerability.
  • Achieves remote code execution on server.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to upload a malicious PHP file to a WordPress site. This file could then be executed, potentially leading to a compromise of the website. The underlying issue involves unprotected API callbacks that allow file uploads without proper validation.

  • Website code execution.
  • Upload malicious files.
  • Full site compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

The payever WooCommerce Gateway plugin's arbitrary file upload vulnerability requires immediate attention from teams responsible for WordPress site security and application code. The first practical step is to identify all WordPress instances using this plugin, assess their exposure and business criticality, and confirm the accountable owner for remediation or mitigation.

  • WordPress application owners.
  • Verify plugin usage and reachability.
  • Plan remediation or implement controls.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the payever WooCommerce Gateway plugin?

It is a WordPress plugin used to integrate the payever payment platform into a WooCommerce store. This component handles transaction synchronization and communication with external payment services, effectively acting as a bridge between your e-commerce site and the payever financial infrastructure.

What is the vulnerability in CVE-2026-93754?

This vulnerability is an Unrestricted Upload of File with Dangerous Type (CWE-434). It means the plugin does not properly check the files sent to it. Because it fails to validate file types before saving them to the server, an attacker can upload an executable script instead of an expected image, leading to remote code execution.

How can an attacker trigger this bug?

An attacker triggers this by sending a request to specific, unauthenticated API callbacks included in the plugin. The process does not require a user account or any special permissions. Simply hitting these endpoints with a crafted file upload request allows the server to store and subsequently run the malicious file.

Why should I care about this vulnerability?

According to Halo Surface Signal, this plugin is part of the public web-accessible surface of a typical WordPress e-commerce deployment. Because these API callbacks are reachable over the internet without authentication, any site using an affected version is directly exposed to external threats.

What is the first step to take if I run this plugin?

Identify all WordPress installations where this plugin is active. Once you have a list of affected sites, assess their business criticality and verify if they are accessible from the public internet. Coordinate with the site owners to plan updates or implement temporary access controls to mitigate the risk of unauthorized file execution.

References