# What PHP2Shell Made Me Think About My 433 MHz Remote **URL:** \ **Category:** News\ **Created:** [October 22, 2026, 6:38am UTC](https://rx480e.discourse.group/t/what-php2shell-made-me-think-about-my-433-mhz-remote/25 "2026-10-22T06:38:10Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Zercher](https://yyz2.discourse-cdn.com/flex012/user_avatar/rx480e.discourse.group/zercher/32/21_2.png) [@Zercher](https://rx480e.discourse.group/u/Zercher)\ **Post date:** [October 22, 2026, 6:38am UTC](https://rx480e.discourse.group/t/what-php2shell-made-me-think-about-my-433-mhz-remote/25/1 "2026-10-22T06:38:10Z")
These past few days, it feels like every other headline has been another vulnerability, and every other website has been rushing to patch. [PHP2Shell](https://www.bleepingcomputer.com/news/security/php-ships-emergency-patches-for-critical-php2shell-flaws/) was the one that caught my eye, with [PHP telling server administrators](https://www.php.net/archive/2026.php#2026-10-21-5) to apply emergency fixes now. Then I looked at the 433 MHz remote on my bench. ![IMG_20261022_143924](https://canada1.discourse-cdn.com/flex012/uploads/rx480e/original/1X/7b295b903ba7ea28d4274100179d803d0d326f46.jpeg) No website, no PHP, no cloud login, and no patches needed tonight. I press a button, my remote sends an EV1527 code, and a paired [RX480E-4](https://qiachip.github.io/qiachip/RX480E/RX480E-4/QIACHIP_RX480E-4/) changes one of its D0-D3 outputs. That is the whole path. I am not saying RF is magically safe. Interference and replay attacks are real, and adding an MCU or cloud gateway means adding another layer to protect. But this contrast is a good reminder to ask: how many controls really need to leave the room? For a project, I like a path I can see, test, and understand. Maybe the web has enough patching to do without making my workshop light apply for a cloud account. What do you keep local?