CAFEHAUS API exposes an unauthenticated password-change route
CAFEHAUS API through 1.0.0 registers POST /wp-json/cafe/v1/user/password/update without a permission_callback. The public handler accepts attacker-controlled userId and password values and passes them to wp_update_user() as ID and user_pass, allowing an unauthenticated attacker to replace any user's password, including an administrator's, and take over the account.
- Component
- CAFEHAUS API
- Plugin slug
cafe-api- Affected
- <= 1.0.0
- Safe version
- See mitigation notes
- Published
- Jul 24, 2026
This CVE was published Jul 24, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
No fixed public release is currently available. Disable CAFEHAUS API or remove the user/password/update route. An application patch should require authentication in permission_callback, authorize the caller against the requested userId and use WordPress's established password-change or reset flow instead of accepting an arbitrary target ID.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The CAFEHAUS API WordPress plugin through 1.0.0 does not have any authentication or authorisation when updating user passwords, allowing unauthenticated attackers to set the password of any user, including administrators, and fully take over their accounts.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H