Mgosync
Monthly
Unauthenticated, network-reachable attackers can read the WooCommerce API consumer key and secret stored by the MgoSync WordPress plugin in any version before 2.1.7, because one of its REST API endpoints performs no authorization check (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Exploitation is trivial and publicly available exploit code exists, though the leak only yields credentials on sites that have completed the MgoSync WooCommerce credential setup; from there, read/write access to the connected store's REST API further depends on that API being reachable and the leaked key retaining its original scope. The vendor has released 2.1.7, and because the exposed key is read/write, credential rotation - not patching alone - is required to close the exposure.
Unauthenticated, network-reachable attackers can read the WooCommerce API consumer key and secret stored by the MgoSync WordPress plugin in any version before 2.1.7, because one of its REST API endpoints performs no authorization check (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Exploitation is trivial and publicly available exploit code exists, though the leak only yields credentials on sites that have completed the MgoSync WooCommerce credential setup; from there, read/write access to the connected store's REST API further depends on that API being reachable and the leaked key retaining its original scope. The vendor has released 2.1.7, and because the exposed key is read/write, credential rotation - not patching alone - is required to close the exposure.