iPOSpays Gateways WC <= 1.3.7 - Unauthenticated Missing Authorization to Settings Update via REST API Endpoint
Strategic Overview
- Status
- Patched in 1.3.8
- Affected Plugin
- iPOSpays Payment Gateway for WooCommerce
- Affected Version
<= 1.3.7- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-39608
At a glance
CVE-2026-39608 is a medium-severity Missing Authorization vulnerability in the iPOSpays Payment Gateway for WooCommerce WordPress plugin, affecting versions <= 1.3.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.8; sites on affected versions should update now. Disclosed February 2026, reported by Legion Hunter.
Vulnerability Overview
The iPOSpays Gateways WC plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 1.3.7. This is due to the plugin exposing a REST API endpoint /wp-json/ipospays/v1/save_settings with 'permission_callback' set to '__return_true', which allows unauthenticated access without any capability checks or nonce verification. This makes it possible for unauthenticated attackers to update plugin settings, specifically allowing them to overwrite critical payment gateway settings including live API keys, secret keys, and payment tokens stored in the 'woocommerce_ipospays_settings' option.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
iPOSpays Payment Gateway for WooCommerce <= 1.3.7 carries this weakness at permission_callback, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For iPOSpays Payment Gateway for WooCommerce the fix is 1.3.8: builds <= 1.3.7 are affected, anything from 1.3.8 onward is not.
Remediation
Update to version 1.3.8, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: iPOSpays Payment Gateway for WooCommerce 1.3.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C