Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've found this code in the plugin (line 1433 and onwards in the latest wordpress plugin version):</p> <pre><code>// check posted input for email injection attempts // Check for these common exploits // if you edit any of these do not break the syntax of the regex $input_expl = "/(content-type|mime-version|content-transfer-encoding|to:|bcc:|cc:|document.cookie|document.write|onmouse|onkey|onclick|onload)/i"; // Loop through each POST'ed value and test if it contains one of the exploits fromn $input_expl: foreach($_POST as $k =&gt; $v){ if (is_string($v)){ $v = strtolower($v); $v = str_replace('donkey','',$v); // fixes invalid input with "donkey" in string $v = str_replace('monkey','',$v); // fixes invalid input with "monkey" in string if( preg_match($input_expl, $v) ){ return __('Illegal characters in POST. Possible email injection attempt', 'si-contact-form'); } } } </code></pre> <p>The error occurs when at least one of the posted fields contain an 'invalid' value anywhere in the string. The most likely candidates that trigger this error on email addresses would seem to be onmouse, onkey, onclick, and onload. (Note that the words 'donkey' and 'monkey' are allowed.) You should check the value of <code>$v</code> just before the return statement so you can determine which section causes the error, then you can decide how to solve the problem.</p> <pre><code> if( preg_match($input_expl, $v) ){ var_dump($v); exit(); // &lt;-- add this for testing return __('Illegal characters in POST. Possible email injection attempt', 'si-contact-form'); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POIllegal characters in POST. Possible email injection attempt error
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USArjan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIllegal characters in POST. Possible email injection attempt error
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI could buy you a big pint of beer! Ok so if my clients name by some AMAZING law if fate was irish and - no kidding 'Mcconkey' that might cause a little problem!
      singulars
      1. PO
      1. USDave
    2. COThank you Arjan. What a relief!
      singulars
      1. PO
      1. USDave
    3. COThe best solution would be to replace `|onkey|` with `|\bonkey|` so it only matches onkey at the beginning of a word, not in the middle. That means McConkey is safe. And maybe you should inform Mike Challis too, so he can fix it for coming versions.
      singulars
      1. PO
      1. USArjan
 

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