Title: improper JavaScript tag placement in HTML code
Last modified: July 26, 2020

---

# improper JavaScript tag placement in HTML code

 *  Resolved [Eli](https://wordpress.org/support/users/scheeeli/)
 * (@scheeeli)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/improper-javascript-tag-placement-in-html-code/)
 * I had someone report that my plugin was finding problem in this file …/controllers/
   twofa/mo2fa_inline_registration.php.
 * The problem that I found was that you have JavaScript tags after the closing 
   </body> tag. This is improper HTML coding, nothing should ever go between the
   </body> and </html> tags. While this kind of sloppy placement of <script> tags
   is usually forgiven by most browsers, and you code will likely work as intended
   in most cases, it is still improper and usually only malicious scripts are injected
   in the wrong place like that. I am giving you this information so that you might
   move your scripts to inside the BODY in your next release.
 * I found this issue on lines 207, 343, 628, 830, 943, 1076, and 1208.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fimproper-javascript-tag-placement-in-html-code%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [miniOrange](https://wordpress.org/support/users/cyberlord92/)
 * (@cyberlord92)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/improper-javascript-tag-placement-in-html-code/#post-13173399)
 * Hi,
 * Thank you for reaching out to us.
 * Thank you for pointing it and taking time to check the plugin. We will update
   this with our next release. We have a release on next week so you can verify 
   it with that.
 * Also if you need any assistance with the plugin you can send us a support request
   from the plugin or our website. We would be happy to assist you.
 *  Plugin Author [miniOrange](https://wordpress.org/support/users/cyberlord92/)
 * (@cyberlord92)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/improper-javascript-tag-placement-in-html-code/#post-13257927)
 * Hi Scheeeli,
 * We have resolved it in the latest version.
 * Please find it and let us know if you have any questions.
 * You can always reach out to us in the future whenever you have any doubts or 
   concerns.
    You can also find us under the Support section of the plugin.
 * We are always here to help you.
 *  Thread Starter [Eli](https://wordpress.org/support/users/scheeeli/)
 * (@scheeeli)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/improper-javascript-tag-placement-in-html-code/#post-13258328)
 * Looks good now. Thanks for the update!

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

The topic ‘improper JavaScript tag placement in HTML code’ is closed to new replies.

 * ![](https://ps.w.org/miniorange-2-factor-authentication/assets/icon-256x256.gif?
   rev=2652528)
 * [miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator)](https://wordpress.org/plugins/miniorange-2-factor-authentication/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/miniorange-2-factor-authentication/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/miniorange-2-factor-authentication/)
 * [Active Topics](https://wordpress.org/support/plugin/miniorange-2-factor-authentication/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/miniorange-2-factor-authentication/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/miniorange-2-factor-authentication/reviews/)

## Tags

 * [2fa](https://wordpress.org/support/topic-tag/2fa/)
 * [mfa](https://wordpress.org/support/topic-tag/mfa/)
 * [TFA](https://wordpress.org/support/topic-tag/tfa/)

 * 3 replies
 * 2 participants
 * Last reply from: [Eli](https://wordpress.org/support/users/scheeeli/)
 * Last activity: [5 years, 9 months ago](https://wordpress.org/support/topic/improper-javascript-tag-placement-in-html-code/#post-13258328)
 * Status: resolved