Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The general rule/meme is "Filter Input, Escape Output." Using <code>strip_tags</code> on your input to remove any HTML is a good idea for input filtering, but you should be as strict as possible in what input you allow. For example, if an input parameter is only supposed to be an integer, only accept numeric input and always convert it to an integer before doing <em>anything</em> with it. A well-vetted input filtering library is going to help you a lot here; one that isn't specific to a particular framework is <a href="http://inspekt.org" rel="nofollow noreferrer">Inspekt</a> (which I wrote, so I'm a bit biased).</p> <p>For output, <code>htmlspecialchars</code> <em>should</em> be able to escape XSS attacks, <strong>but only if you pass the correct parameters</strong>. You must pass the quote escaping style <em>and</em> a charset.</p> <p>In general, this <em>should</em> remove XSS attacks:</p> <pre><code>$safer_str = htmlspecialchars($unsafe_str, ENT_QUOTES, 'UTF-8'); </code></pre> <p>Without passing <code>ENT_QUOTES</code> as the second parameter, single-quote chars are not encoded. Additionally, XSS attacks have been demonstrated when the correct charset is not passed (typically UTF-8 will be adequate). <code>htmlspecialchars</code> should <em>always</em> be called with ENT_QUOTES and a charset parameter.</p> <p>Note that PHP 5.2.12 contains a fix for <a href="http://bugs.php.net/bug.php?id=49785" rel="nofollow noreferrer">a multibyte XSS attack</a>.</p> <p>You may find the <a href="http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API" rel="nofollow noreferrer">OWASP ESAPI PHP port</a> interesting and useful, although the PHP version is not complete AFAIK.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs preventing XSS and SQL Injection as easy as does this
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USFunkatron
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@Funkatron, so is my updated original post protect me from all evil?
      singulars
      1. PO
      1. USTimTim
    2. COIt looks to be relatively safe, yes.
      singulars
      1. PO
      1. USFunkatron
    3. COI don't think `strip_tags` is a good idea. It breaks some legitimate input, but isn't sufficient for security. Just `htmlspecialchars()` suffices and it's not lossy.
      singulars
      1. PO
      1. USKornel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload