Using PHP_SELF in the action field of a form

In this article shows the usage of PHP_SELF variable and how to avoid PHP_SELF exploits.

What is PHP_SELF variable?

PHP_SELF is a variable that returns the current script being executed. This variable returns the name and path of the current file (from the root folder). You can use this variable in the action field of the FORM. There are also certain exploits that you need to be aware of. We shall discuss all these points in this article.

We will now see some examples.
echo $_SERVER['PHP_SELF'];

a) Suppose your php file is located at the address:

In this case, PHP_SELF will contain:

b) Suppose your php file is located at the address:

For this URL, PHP_SELF will be :

Using the PHP_SELF variable in the action field of the form

A common use of PHP_SELF variable is in the action field of the <form> tag. The action field of the FORM instructs where to submit the form data when the user presses the “submit” button. It is common to have the same PHP page as the handler for the form as well.

However, if you provide the name of the file in the action field, in case you happened to rename the file, you need to update the action field as well; or your forms will stop working.

Using PHP_SELF variable you can write more generic code which can be used on any page and you do not need to edit the action field.

Consider, you have a file called form-action.php and want to load the same page after the form is submitted. The usual form code will be:

<form  method="post" action="form-action.php" >

We can use the PHP_SELF variable instead of “form-action.php”. The code becomes:

<form name="form1" method="post" action="<?php echo $_SERVER['PHP_SELF']; ?>" >

The complete code of “form-action.php”

Here is the combined code, that contains both the form and the PHP script.

    $name = $_POST['name'];
    echo "User Has submitted the form and entered this name : <b> $name </b>";
    echo "<br>You can use the following form again to enter a new name."; 
<form method="post" action="<?php echo $_SERVER['PHP_SELF']; ?>">
   <input type="text" name="name"><br>
   <input type="submit" name="submit" value="Submit Form"><br>

This PHP code is above the HTML part and will be executed first. The first line of code is checking if the form is submitted or not. The name of the submit button is “submit”. When the submit button is pressed the $_POST['submit'] will be set and the IF condition will become true. In this case, we are showing the name entered by the user.

If the form is not submitted the IF condition will be FALSE as there will be no values in $_POST['submit'] and PHP code will not be executed. In this case, only the form will be shown.

What are PHP_SELF exploits and how to avoid them

The PHP_SELF variable is used to get the name and path of the current file but it can be used by the hackers too. If PHP_SELF is used in your page then a user can enter a slash (/) and then some Cross Site Scripting (XSS) commands to execute.

See below for an example:

<form name="test" action="<?php echo $_SERVER['PHP_SELF']; ?>" method="post">

Now, if a user has entered the normal URL in the address bar like
the above code will be translated as:

<form name="test" action="form-action.php" method="post">

This is the normal case.

Now consider that the user has called this script by entering the following URL in the browser’s address bar:'xss')%3C

In this case, after PHP processing the code becomes:

<form name="test" method="post" action="form-action.php"/>

You can see that this code has added a script tag and an alert command. When this page is be loaded, user will see an alert box. This is just a simple example how the PHP_SELF variable can be exploited.

Any JavaScript code can be added between the “script” tag. <script>....HERE....</script>. A hacker can link to a JavaScript file that may be located on another server. That JavaScript file can hold the malicious code that can alter the global variables and can also submit the form to another address to capture the user data, for example.

How to Avoid the PHP_SELF exploits

PHP_SELF exploits can be avoided by using the htmlentities() function. For example, the form code should be like this to avoid the PHP_SELF exploits:

<form name="test" action="<?php echo htmlentities($_SERVER['PHP_SELF']); ?>" method="post">

The htmlentities() function encodes the HTML entities. Now if the user tries to exploit the PHP_SELF variable, the attempt will fail and the result of entering malicious code in URL will result in the following output:

<form name="test" method="post" 

As you can see, the script part is now ‘sanitized’.

So don’t forget to convert every occurrence of "$_SERVER['PHP_SELF']" into "htmlentities($_SERVER['PHP_SELF'])" throughout your script.

Some PHP servers are configured to solve this issue and they automatically do this conversion.But, why take risk? make it a habit to use htmlentities() with PHP_SELF.

Comments on this entry are closed.

  • Leave it blank. No problem occurs.
    Thnks for the tut.

  • Very useful trick. Thanks for posting!

  • Thanks for the tip! I am just now getting into PHP and it was nice to see that this was an option – before that, I was defining the pages manually and having to change declarations when I swapped documents and stuff. This has really made everything easier to manage.

  • Nice article. Very well written. Thanks!

  • I was searching this..Thank you

  • what if i leave the option option blank?

    it do the same thing and wohtout any risk u code is safe

  • HTML5 doesn’t like the blank string. But you can leave the parameter off altogether. I’m about to go test if you can have ACTION ACTION=”” in the same tag for 2-way compliance.

  • this is really helpfulllllll………….thanks

  • Thanks for the advice.

    There’s another problem with using $_SERVER[‘PHP_SELF’] in the action section of a form – I use Javascript to change the action to open a new window with a page that uses form info from the calling page. (this way I can have a form with buttons each one using the same form fields but going to different pages – like a menu page that needs to pass on information) When I submit the form after the javascript has changed the action it goes to the javascript changed location whereas if you hard code the action page it goes to where you coded.

  • Thanks for the tut,…

  • Thanks a lot for that. You are doing a good job.

  • Your explanation is too good to understand about php_self.but i’ve one doubt is why you specified the html form code after the php code. is that thing mandatory??
    can you expalin it more clearly about that.

    thanx in advance.