Title: Plugin Security Vulnerability
Last modified: August 11, 2022

---

# Plugin Security Vulnerability

 *  Resolved [yyz9](https://wordpress.org/support/users/yyz9/)
 * (@yyz9)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/plugin-security-vulnerability/)
 * I use a plugin called Malcare to check for security vulnerabilities and it keeps
   identifying Header Footer Code Manager as “this item is vulnerable.” Based on
   the reviews – This is coming across as a surprise – But need to ask if there 
   have been any instances of any Malware associated with the plugin? Do I need 
   to do anything differently?

Viewing 1 replies (of 1 total)

 *  Plugin Author [DraftPress Team](https://wordpress.org/support/users/draftpress/)
 * (@draftpress)
 * [3 years, 9 months ago](https://wordpress.org/support/topic/plugin-security-vulnerability/#post-15911247)
 * Hi [@yyz9](https://wordpress.org/support/users/yyz9/) – There were some minor
   issues with the plugin, we already worked with WordPress and resolved them. You
   can use HFCM without any worries.
 * Thank you.

Viewing 1 replies (of 1 total)

The topic ‘Plugin Security Vulnerability’ is closed to new replies.

 * ![](https://ps.w.org/header-footer-code-manager/assets/icon-256x256.png?rev=2681303)
 * [Header Footer Code Manager](https://wordpress.org/plugins/header-footer-code-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/header-footer-code-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/header-footer-code-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/header-footer-code-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/header-footer-code-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/header-footer-code-manager/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [DraftPress Team](https://wordpress.org/support/users/draftpress/)
 * Last activity: [3 years, 9 months ago](https://wordpress.org/support/topic/plugin-security-vulnerability/#post-15911247)
 * Status: resolved