<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web-App-Security on CuraSec</title><link>https://curasec.metacog.co.kr/tags/web-app-security/</link><description>Recent content in Web-App-Security on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 15:52:23 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/web-app-security/index.xml" rel="self" type="application/rss+xml"/><item><title>PHP2Shell zero-day exploited 4 days before patches shipped</title><link>https://curasec.metacog.co.kr/insights/2026-10-22-amazon-says-php2shell-exploitation-began-4-days-before-patch/</link><pubDate>Thu, 22 Oct 2026 15:52:23 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-22-amazon-says-php2shell-exploitation-began-4-days-before-patch/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Patches are now available and exploitation was actively occurring before release — patch PHP2Shell to the latest version immediately and audit any exposed instances for signs of compromise during the 4-day pre-patch window.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Pre-patch exploitation means potential compromises predate any patching activity; initiate a retroactive hunt across web server logs and EDR telemetry covering at least the 4 days before Wednesday&amp;rsquo;s patch release for PHP2Shell-related activity.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>