On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-93754, affects the payever - WooCommerce Gateway plugin for WordPress in versions up to and including 4.8.0. According to the GitHub Advisory Database entry, unauthenticated attackers can write an executable PHP file to the site and achieve remote code execution.
If you run a WooCommerce store that uses this payment gateway, treat this as urgent. The advisory does not list a patched version, and the public record does not say whether the flaw is being exploited, so the safest assumption is that exposed sites should be protected now.
What happened
The advisory was published on November 7, 2026 and describes an arbitrary file upload flaw in the payever gateway plugin. The same text appears in the NVD record, but NVD repeats the GitHub advisory rather than confirming it independently. So far only this single description of the issue is available, and the GitHub entry is marked as unreviewed.
The attack needs no account, no special privileges and no user interaction, and it can be launched over the network with low complexity. That combination is what produces the 9.8 score.
Technical details in plain terms
Two weaknesses combine here. The first is missing access control. Three WooCommerce API callbacks named payever_set_sandbox_api_keys, payever_toggle_subscription and payever_synchronization_incoming are registered with no authentication, no capability check and no nonce. In practice, anyone on the internet can call them, not just a logged-in shop administrator.
The second is an upload routine that does things in the wrong order. The advisory says the upload_image() function writes a remotely fetched file into the public uploads directory, using a filename the attacker controls, before it checks the file type. If the saved file ends in .php and the web server executes PHP from that location, the attacker has a working web shell, which means full control over the site's code and data.
Who is affected
Any WordPress site with the payever - WooCommerce Gateway plugin active at version 4.8.0 or earlier is in scope. The advisory says "various versions up to, and including, 4.8.0" and does not state the oldest affected version, so do not assume an older release is safe. Because the vulnerable callbacks are part of the plugin's normal registration, a site generally does not need unusual settings to be exposed, though the research does not spell out the exact conditions.
Stores carry extra risk. A web shell on a checkout site can expose customer data, alter payment pages or be used to plant card skimmers. See our guide to card skimming for why that matters.
How to check your exposure
Start by confirming whether the plugin is installed and which version you run. This WP-CLI command lists the plugin's status and version from the WordPress root directory. It is read-only. Look for a version of 4.8.0 or lower.
wp plugin list --name=payever-woocommerce-gateway --fields=name,status,versionNext, look for unexpected PHP files in the uploads directory, where WordPress normally stores only media. This read-only find command, run from the WordPress root, lists any .php files under wp-content/uploads. On a healthy site it should return nothing, so investigate any result.
find wp-content/uploads -type f -name "*.php"Also review your web server access logs for requests to the three callback names listed above. This grep prints matching lines from an access log; adjust the path to your server. Matches are not proof of compromise, but unexpected hits from unfamiliar addresses deserve a closer look.
grep -E "payever_set_sandbox_api_keys|payever_toggle_subscription|payever_synchronization_incoming" /var/log/nginx/access.logWhat to do now
No fixed version is named in the advisory, so the actions below focus on reducing exposure and checking for compromise. The advisory references a plugin changeset, but it does not say that this contains a fix. Check the plugin's page in the WordPress directory and the vendor's notes for a release newer than 4.8.0.
- Confirm whether the payever - WooCommerce Gateway plugin is installed and note its version.
- Take a full backup of files and database before you change anything.
- Check for an update newer than 4.8.0 and install it if one exists. If none is available, deactivate and remove the plugin until the vendor confirms a fix.
- Search wp-content/uploads for .php files and review recent file changes elsewhere in the site.
- Review access logs for requests to the three callback names and for unfamiliar POST requests around the time the advisory was published.
- If you find a suspicious file or any sign of intrusion, follow an incident process: isolate the site, remove the malicious files, and rotate WordPress admin, database, hosting and payment API credentials.
- Block PHP execution in the uploads directory at the web server level as a defense in depth measure, after testing that your media still works.
- Consider a web application firewall to filter malicious requests while you wait for a vendor fix.
If you suspect the site has already been compromised, our guides on what to do when a website is hacked and how to check if a website is hacked walk through containment and cleanup.
Detection and monitoring afterwards
Remote code execution flaws often leave quiet footholds, so keep watching after you have removed or updated the plugin. Re-run the uploads directory check regularly, and keep file integrity or change alerts on your WordPress directories if your host offers them. Watch for new admin users, unfamiliar scheduled tasks and unexpected outbound connections.
For stores, alerts for new scripts on checkout pages help catch tampering that follows a server compromise; see alerts for new scripts on checkout pages. You can also keep an eye on known issues for other plugins you use through the WordPress plugin vulnerability list and the WordPress security checklist.
What is still unknown
- Which version, if any, fixes the issue. The advisory lists patched versions as unknown.
- The earliest affected version. The text says only "various versions" up to 4.8.0.
- Whether attacks are happening. The research does not report exploitation, and no CISA KEV entry is listed.
- Independent confirmation. NVD repeats the GitHub description, and the GitHub entry is marked unreviewed.
We will update this article if the vendor or other researchers publish a patched release or evidence of exploitation.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
