Ive checked all my self hosted services and was happy to find out the only one was written in PHP, addy, formerly anonaddy.

You can use the awesome self hosted GitHub repo or this one already filtered for PHP

https://awesome-selfhosted.net/platforms/php.html

all 17 comments

sorted by: hot top controversial new old
[–] 3 points 10 hours ago

Roundcube and Baikal for me. I used Mutt for email today 😂

  • source
  • [–] 2 points 10 hours ago*

    Browsing through the list... ok how do I tell if my server has been compromised, because I run a fuckload of those...

  • source
  • [–] 39 points 20 hours ago (3 children)

    I also maintain a language filter over at selfh.st/apps that can be used to identify PHP-heavy platforms:

    https://selfh.st/apps/?language=PHP

  • source
  • hideshow 3 child comments
  • [–] 2 points 17 hours ago (1 child)

    One I know about that's not on your list and is very likely to be an exposed service is Mailcow. Looks like the PHP filter isn't triggering for it, but it's definitely PHP based.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 15 hours ago*

    Good call-out. The directory pulls the prominent language from each project's repo, which is JavaScript for Mailcow.

    I should update the dataset to grab any languages above a certain % threshold (25%?) to prevent instances like this where something might fall through the cracks.

  • source
  • parent
  • [–] 2 points 12 hours ago

    Synology includes some php runtime or package they require... I think... But I dont expose my services outside.

  • source
  • [–] 2 points 12 hours ago

    Phew, nextcloud and freshrss both have updates to resolve the vulnerability. Furiously logs in to update

  • source
  • [–] 3 points 14 hours ago
    [–] 15 points 20 hours ago* (1 child)

    That list isn't completely accurate for what you're after. My project, for instance, is not on the PHP list despite it being written in PHP because the platform is Docker. The selfh.st filter as described by eshol might be the better way to go.

  • source
  • hideshow 1 child comment
  • [–] 10 points 19 hours ago (2 children)

    My Nextcloud is the only public facing service on the list. Is it sufficient to just disable public access via Nginx Proxy Manager and continue to permit local access for Nextcloud, or do I need to just shut down Nextcloud until it gets updated?

  • source
  • hideshow 2 child comments
  • [–] 11 points 18 hours ago

    Public access is what is in immediate danger. Private services are safe from bots, but at risk from attacker on your network - a compromised IoT device or package on server could move laterally to vulnerable PHP services

  • source
  • parent
  • [–] 12 points 20 hours ago*

    None of my stuff is publicly accessible so yay for not having to take anything offline.

    There are quite a few things offline in NL because of this though.

  • source
  • [–] 4 points 20 hours ago

    The good thing about it is that all PHP applications run through a single service (unless you use containers for each of them individually, I guess), so it's really easy to take them all down at the same time, and update them all at once.

  • source
  • [–] 2 points 18 hours ago

    Isn’t zabbix missing ? Just from the top of my mind

  • source