# PHP vulnerability impact write.as?

**URL:** <https://discuss.write.as/t/php-vulnerability-impact-write-as/21258>\
**Category:** General\
**Created:** [October 21, 2026, 3:58pm UTC](https://discuss.write.as/t/php-vulnerability-impact-write-as/21258 "2026-10-21T15:58:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![justinf](https://discuss.write.as/user_avatar/discuss.write.as/justinf/32/1242_2.png) [@justinf](https://discuss.write.as/u/justinf)\
**Post date:** [October 21, 2026, 3:58pm UTC](https://discuss.write.as/t/php-vulnerability-impact-write-as/21258/1 "2026-10-21T15:58:29Z")

</div>

@matt , does all this PHP vulnerability stuff impact write.as? It’s pretty wild.

 ![SCR-20261021-ijbn](https://discuss.write.as/uploads/default/original/2X/d/dca8e49f605f8d0f7a354ac8d48cb9480a795026.png)

---

<div class="post-metadata">

**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\
**Post date:** [October 21, 2026, 4:55pm UTC](https://discuss.write.as/t/php-vulnerability-impact-write-as/21258/2 "2026-10-21T16:55:27Z")

</div>

We don’t use PHP anywhere (everything is written in Go), so we shouldn’t be affected by this. But yeah, the amount of security vulnerabilities coming out this year has been dizzying.