Title: kyle_t's Replies | WordPress.org

---

# kyle_t

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

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

 Search replies:

## Forum Replies Created

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

 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [$_GET['m'] for custom use instead of month](https://wordpress.org/support/topic/_getm-for-custom-use-instead-of-month/)
 *  [kyle_t](https://wordpress.org/support/users/kyle_t/)
 * (@kyle_t)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/_getm-for-custom-use-instead-of-month/#post-5392038)
 * The reason why it wasn’t letting you use ‘m’ as a GET variable is because it 
   is already reserved by wordpress, see full list of reserved variable names here:
   [http://codex.wordpress.org/Function_Reference/register_taxonomy#Reserved_Terms](http://codex.wordpress.org/Function_Reference/register_taxonomy#Reserved_Terms)
 * “Avoiding the following reserved terms is particularly important if you are passing
   the term through the $_GET or $_POST array. Doing so can cause WordPress to respond
   with a 404 error without any other hint or explanation.”
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Possible Security Vunerability: admin-bar.php](https://wordpress.org/support/topic/possible-security-vunerability-admin-barphp/)
 *  [kyle_t](https://wordpress.org/support/users/kyle_t/)
 * (@kyle_t)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/possible-security-vunerability-admin-barphp/#post-4985459)
 * I don’t see any issue, as of now. Obviously these files are not supposed to be
   accessed directly, and accessing admin-bar.php directly doesn’t do much since
   the add_action() function is not defined within that file. (It is defined in 
   wp-includes/plugin.php)
 * But I’m going way out on a limb here and saying maybe there is a plugin or some
   other malware that makes an edit to that file so that when that file is accessed
   directly it leads to a backdoor into wordpress admin. Again just speculation 
   and also worst case scenario.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Possible Security Vunerability: admin-bar.php](https://wordpress.org/support/topic/possible-security-vunerability-admin-barphp/)
 *  [kyle_t](https://wordpress.org/support/users/kyle_t/)
 * (@kyle_t)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/possible-security-vunerability-admin-barphp/#post-4985445)
 * I was able to recreate the error in the error logs with our ip by visiting /wp-
   includes/admin-bar.php directly, I did not try posting any data to it
    I have
   to agree with another guy that the site is not hacked, it is just an attempt 
   to exploit.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Possible Security Vunerability: admin-bar.php](https://wordpress.org/support/topic/possible-security-vunerability-admin-barphp/)
 *  [kyle_t](https://wordpress.org/support/users/kyle_t/)
 * (@kyle_t)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/possible-security-vunerability-admin-barphp/#post-4985440)
 * I have been noticing the same error coming through our logs. I am interested 
   in any more information that you find about this attempted exploit.

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