[wp-trac] Re: [WordPress Trac] #4012: XSS on page-new.php

[WordPress Trac]

#4012: XSS on page-new.php
--------------------------------------+-------------------------------------
 Reporter:  xknown                    |        Owner:  anonymous
     Type:  defect                    |       Status:  reopened 
 Priority:  highest omg bbq           |    Milestone:  2.1.3    
Component:  Security                  |      Version:  2.1.2    
 Severity:  normal                    |   Resolution:           
 Keywords:  2nd-opinion dev-feedback  |  
--------------------------------------+-------------------------------------
Changes (by charleshooper):

  * keywords:  => 2nd-opinion dev-feedback
  * status:  closed => reopened
  * resolution:  fixed =>
 * cc: charleshooper (added)

Comment:

 Not to step on any toes as I understand this is a high priority item,
 however is casting to int adequate? I'm referring to the fact that
 {{{wp_posts.ID}}} is a BIGINT-sized column and the maximum size integer on
 32-bit systems is 2,147,483,647. Not that I think many people out there
 have over 2 billion posts, but I feel that if we impose a limit (by
 casting a variable to int) then we should update the schema accordingly.
 Think of it as a SQL optimization if you must.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/4012#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software