Description:Muhammad Daffa discovered and reported this Cross Site Request Forgery (CSRF) vulnerability in WordPress Side Cart Woocommerce (Ajax) Plugin. This could allow a malicious actor to force higher privileged users to execute unwanted actions under their current authentication. For example a password change which will then allow the malicious actor to login into the admin account.
WordFence reporting it as well. I’m still parsing this:
The Side Cart Woocommerce (Ajax) plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1. This is due to missing or incorrect nonce validation on one of its functions. This makes it possible for unauthenticated attackers to invoke this function and reset the plugin’s settings, via forged request granted they can trick a site administrator into performing an action such as clicking on a link. Please note that the developer released a patch, but did not update the patched version so it is both vulnerable and patched in version 2.1.
…Saw somewhere that it was initially reported a month ago – last update to this plugin was 7 days ago… but the developer has removed all mention of this plugin on their site as they look to have moved attention to a paid version?
Thanks for the quick response, and apologies I didn’t see it on your site. I wondered if a full delete and reinstall was to be the next step, but that odd verbage in the WordFence description threw me.
Hi @xootix but Wordfence still reports as critical:
They say on their site this:
Description
The Side Cart Woocommerce (Ajax) plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1. This is due to missing or incorrect nonce validation on one of its functions. This makes it possible for unauthenticated attackers to invoke this function and reset the plugin’s settings, via forged request granted they can trick a site administrator into performing an action such as clicking on a link. Please note that the developer released a patch, but did not update the patched version so it is both vulnerable and patched in version 2.1.
So 2.1 is still sort of really not patched for them.
How can I solve not getting this error every time the Worfence scan runs?
This reply was modified 3 years, 2 months ago by baltas.
This reply was modified 3 years, 2 months ago by baltas.
Also deleted and reinstalled and still getting the same critical vulnerability warning. Also getting warnings that the following files differed from the repo:
