Syncee for Suppliers <= 1.0.5 - Missing Authorization to Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 1.0.10
- Affected Plugin
- Syncee for Suppliers
- Affected Version
<= 1.0.5- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a medium-severity Missing Authorization vulnerability in the Syncee for Suppliers WordPress plugin, affecting versions <= 1.0.5. 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.0.10; sites on affected versions should update now. Disclosed October 2022.
Vulnerability Overview
The Syncee for Suppliers plugin for WordPress is vulnerable to Missing Authorization to Sensitive Information Disclosure in versions up to, and including, 1.0.5. This is due to a missing capability check on the /wp-json/syncee/supplier/v1/getDataForFrontend REST-API endpoint. This makes it possible for unauthenticated attackers to perform a GET request to that information that discloses information like the site's syncee_access_token_supplier and data_to_syncee_installer_supplier values.
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
Reaching this weakness in Syncee for Suppliers <= 1.0.5 takes a caller who can reach the endpoint. 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 Syncee for Suppliers the fix is 1.0.10: builds <= 1.0.5 are affected, anything from 1.0.10 onward is not.
Remediation
Update to version 1.0.10, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Syncee for Suppliers 1.0.10 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