WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #3243


Ignore:
Timestamp:
10/14/2006 05:45:08 AM (14 years ago)
Author:
markjaquith
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3243

    • Property Status changed from new to assigned
  • Ticket #3243 – Description

    initial v1  
    66
    77 1. It is safer.
    8   #. Worst case scenario with assuming data to be unescaped is that it gets double slashed
    9   #. Worst case scenario with assuming data to be '''escaped''' is SQL injection vulnerability
     8   * Worst case scenario with assuming data to be unescaped is that it gets double slashed
     9   * Worst case scenario with assuming data to be '''escaped''' is SQL injection vulnerability
    1010 2. Post meta has been doing it this way, for a longer time, so less code would have to change
    1111 3. It would allow code consolidation, in terms of handling arrays/objects/strings, serialization, and escape.