Title: rtcbad's Replies | WordPress.org

---

# rtcbad

  [  ](https://wordpress.org/support/users/rtcbad/)

 *   [Profile](https://wordpress.org/support/users/rtcbad/)
 *   [Topics Started](https://wordpress.org/support/users/rtcbad/topics/)
 *   [Replies Created](https://wordpress.org/support/users/rtcbad/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/rtcbad/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/rtcbad/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/rtcbad/engagements/)
 *   [Favorites](https://wordpress.org/support/users/rtcbad/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Version 3.9.4](https://wordpress.org/support/topic/version-3-9-4/)
 *  [rtcbad](https://wordpress.org/support/users/rtcbad/)
 * (@rtcbad)
 * [5 years ago](https://wordpress.org/support/topic/version-3-9-4/#post-14670216)
 * [@oskam](https://wordpress.org/support/users/oskam/),
 * There was a recent critical vulnerability found, detailed here:
 * [https://woocommerce.com/posts/critical-vulnerability-detected-july-2021/](https://woocommerce.com/posts/critical-vulnerability-detected-july-2021/)
 * As noted in that blog post, WooCommerce pushed out updates to each of the release
   branches. This is why you saw your WooCommerce plugin updated from whatever previous
   3.9.x version you were running, to this latest 3.9.4 release branch.
 * As you can see, this is good since your site is now no longer affected by that
   critical vulnerability! Also, as [@rainfallnixfig](https://wordpress.org/support/users/rainfallnixfig/)
   recommended, it would still be a good idea to update your WordPress, WooCommerce,
   and other plugins and themes, to the latest versions as soon as feasible.
 * I Hope this helps explain the situation!
    -  This reply was modified 5 years ago by [rtcbad](https://wordpress.org/support/users/rtcbad/).
      Reason: Reiterate need to stay up-to-date
    -  This reply was modified 5 years ago by [rtcbad](https://wordpress.org/support/users/rtcbad/).
      Reason: fix grammar
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Wordfence is not “supported” by WP and has been disabled automatically](https://wordpress.org/support/topic/wordfence-is-not-supported-by-wp-and-has-been-disabled-automatically/)
 *  [rtcbad](https://wordpress.org/support/users/rtcbad/)
 * (@rtcbad)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/wordfence-is-not-supported-by-wp-and-has-been-disabled-automatically/#post-10146675)
 * You are welcome [@wfasa](https://wordpress.org/support/users/wfasa/)!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Possible bug Wordfence does’t honor disabled “Enable SSL Verification” setting](https://wordpress.org/support/topic/possible-bug-wordfence-doest-honor-disabled-enable-ssl-verification-setting/)
 *  Thread Starter [rtcbad](https://wordpress.org/support/users/rtcbad/)
 * (@rtcbad)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/possible-bug-wordfence-doest-honor-disabled-enable-ssl-verification-setting/#post-10146667)
 * [@wfyann](https://wordpress.org/support/users/wfyann/), thank you for the clarification,
   as I see now that the setting is for SSL _verification_ and not connectivity!
   🙂
 * I will continue to use my workaround until our new servers arrive and we can 
   upgrade and support TLS >= 1.1.
 * Thanks again!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Wordfence is not “supported” by WP and has been disabled automatically](https://wordpress.org/support/topic/wordfence-is-not-supported-by-wp-and-has-been-disabled-automatically/)
 *  [rtcbad](https://wordpress.org/support/users/rtcbad/)
 * (@rtcbad)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/wordfence-is-not-supported-by-wp-and-has-been-disabled-automatically/#post-10139659)
 * There are two kinds of WordPress web sites. Those hosted on WordPress.com’s servers(
   like your site) and those hosted elsewhere. Only web sites hosted on the WordPress.
   com servers are affected by the security plugin restriction you noted. All WordPress
   web sites hosted elsewhere don’t have this restriction.
 * Hope this clarifies the situation!

Viewing 4 replies - 1 through 4 (of 4 total)