Title: Hacking Problem?
Last modified: April 19, 2020

---

# Hacking Problem?

 *  Resolved [m.orange](https://wordpress.org/support/users/morange/)
 * (@morange)
 * [6 years, 1 month ago](https://wordpress.org/support/topic/hacking-problem-4/)
 * Hello W3TotalCache Team,
 * we probably discovered a hacking problem on our site today. Can you say something
   about this …?
    We used the latest WP 5.3.x, use as theme “Themify Parallax” 2.8.3,
   ContactForm7 and W3 Total Cache. The PHP version used is 7.2 and Apache is used
   as the server.
 * We suspect that the activated caching of the theme and the caching by W3 Total
   Cache created a gap through which it was possible to inject code into the contact
   form.
 * The Contactform looked like this: [https://owncloud.dermatthes-frauhofer.de/index.php/s/XG5BvFmqunfjHXn](https://owncloud.dermatthes-frauhofer.de/index.php/s/XG5BvFmqunfjHXn)
 * In the meantime we have imported all updates and deactivated the caching of W3
   Total Cache. It seems that the problem has been found. Is that correct? Can you
   give us more information or do you need more to analyze the problem?
    We are 
   grateful for any help.
 * We know that creating an excellent caching plugin and keeping it safe is not 
   easy. But maybe you can give us some clues as to what to do.
 * Thanks a lot
    Steffen

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [6 years, 1 month ago](https://wordpress.org/support/topic/hacking-problem-4/#post-12698796)
 * Hello [@morange](https://wordpress.org/support/users/morange/)
 * I am sorry about the issue you are experiencing and I am happy to assist you 
   with this.
    First of all, it’s not recommended to use more than one caching solution.
   So you should not use W3 Total Cache minify if you are using a theme minify because
   it can break the styling. As for the having, there is no gap that W3 Total Cache
   creates to allow injecting a code. The reason why that code was removed after
   you disabled W3 Total Cache, or cleared the cache is that that page was cached,
   so W3 Total Cache may have actually helped you identify the issue. Be that as
   it may, this is not related to W3 Total Cache and W3 Total Cache is not responsible
   for this. You can exclude that page from being cache by adding it to “Never cache
   following pages ” filed in Performance>Page cache and add E.G. /contact/ this
   way the page will not be cached. Thank you!

Viewing 1 replies (of 1 total)

The topic ‘Hacking Problem?’ is closed to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

## Tags

 * [Themify](https://wordpress.org/support/topic-tag/themify/)
 * [W3T](https://wordpress.org/support/topic-tag/w3t/)

 * 1 reply
 * 2 participants
 * Last reply from: [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * Last activity: [6 years, 1 month ago](https://wordpress.org/support/topic/hacking-problem-4/#post-12698796)
 * Status: resolved