<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Write-Up on ramenaru's Blog</title><link>https://blog.ramenaru.com/tags/write-up/</link><description>Recent content in Write-Up on ramenaru's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.ramenaru.com/tags/write-up/index.xml" rel="self" type="application/rss+xml"/><item><title>The Old Rumour And PHP2Shell Vulnerability</title><link>https://blog.ramenaru.com/2026/10/the-old-rumour-and-php2shell-vulnerability/</link><pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.ramenaru.com/2026/10/the-old-rumour-and-php2shell-vulnerability/</guid><description>&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt; &lt;em&gt;This writeup is for educational purposes only. Do not test these techniques on systems you do not own or have explicit permission to test. Hacking your neighbor&amp;rsquo;s Wi-Fi is illegal, and so is hacking their website.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I recently spent some time messing around with a newly disclosed vulnerability called PHP2Shell (CVE-2026-109618, CVE-2026-109619). I decided to spin up a local lab and try to exploit it myself to see how dangerous it actually is. Here is a breakdown of my entire process, from the initial scanning to the actual server takeover (the-lab).&lt;/p&gt;</description></item></channel></rss>