Appy Pie Connect for WooCommerce <= 1.1.2 - Missing Authorization to Unauthenticated Privilege Escalation via reset_user_password
Strategic Overview
- Status
- Patched in 1.1.3
- Affected Plugin
- Appy Pie Connect for WooCommerce
- Affected Version
<= 1.1.2- CVSS
- 9.8Critical
- Weakness type
- CWE-620 · Unverified Password Change
- CVE
CVE-2025-9286
At a glance
CVE-2025-9286 is a critical-severity Unverified Password Change vulnerability in the Appy Pie Connect for WooCommerce WordPress plugin, affecting versions <= 1.1.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.1.3; sites on affected versions should update now. Disclosed October 2025, reported by johska.
Vulnerability Overview
The Appy Pie Connect for WooCommerce plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization within the reset_user_password() REST handler in all versions up to, and including, 1.1.2. This makes it possible for unauthenticated attackers to to reset the password of arbitrary users, including administrators, thereby gaining administrative access.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-620: Unverified Password Change
Appy Pie Connect for WooCommerce <= 1.1.2 carries this weakness at reset_user_password(), and reaching it takes no account at all. Unverified password change means the password-update path does not require proof that the requester is the account owner.
An attacker who can reach the endpoint takes over the account outright, and the legitimate owner is locked out of it. For Appy Pie Connect for WooCommerce the fix is 1.1.3: builds <= 1.1.2 are affected, anything from 1.1.3 onward is not.
Remediation
Update to version 1.1.3, 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: Appy Pie Connect for WooCommerce 1.1.3 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