Skip to content

PHP Remote Code Execution

Coop Cloud Security Advisory 20261021-01

Recipes known to be affected >
Recipe Update Status Notes
4get Pending 0.7.4+1.0.62 has been deployed. It's is unclear if it has the fix. Needs to be confirmed.
akaunting Unmaintained There appears to be no owner to fix this.
civicrm-backdrop Unmaintained No updates in 2 years
civicrm-wordpress Pending No update since last year
custom-php Pending
dokuwiki Pending No update in 2 years
drutopia Pending No update in 2 years
engelsystem Unmaintained This is probably unmaintained
farmos Pending No update in 2 years
filerun Pending No update in 2 years
firefly-iii Pending
firefly-iii-importer Pending
h5ai Pending
hauk Pending
invoiceninja Fixed ✅ Fixed at 1.1.0+5.13
kanboard Pending
kimai Fixed ✅ fixed @ 1.14.1+2.70.1
lichen-markdown Not Affected Lichen is uses PHP to generate static pages, and thus is not affected by the vulnerabilites.
limesurvey Pending
mailu Fixed ✅ There's a upstream mitigation fix in abra app deploy foo.bar 3.2.1+2024.06.66 pending an Alpine image upgrade.
matomo Pending
mediawiki Pending
monica Pending
moodle Fixed ✅
mrbs Fixed ✅
nextcloud Fixed ✅ Redeploy 14.6.0+33-fpm or 15.0.0+34.0.5-fpm for update images, fixed in 15.0.1+34.0.5
openemr Pending
osticket Pending
phpservermon Pending
pixelfed Pending
privatebin Pending
projectsend Pending
rallly Not Affected Rallley uses a PHP desrialization library in JavaScript. This may be identified as PHP, but it is in fact node.js
renovate Not Affected the image renovate/renovate:41-full from 1.0.1+41-full has the php-cli, however there don't appear to be php web components in the application.
roundcube Pending
selfoss Pending
shlink Fixed ✅ 1.0.0+5.1
wallabag Pending
wordpress Fixed ✅ Redeploy 4.1.1+7.1.3 for update images
wordpress-bedrock Pending

Check if your deployment is affected

  1. Review the affected recipes list above.
  2. For each app, run abra app run <APP_DOMAIN> app -- php -v and compare to the recommended versions:

    PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical vulnerabilities that can allow unauthenticated remote code execution. All PHP users are strongly encouraged to update immediately. — https://www.php.net/archive/2026.php#2026-10-21-5

Mitigation

Warning

Several of the upstream app updates have been released without changes in the Docker version ("tag") number — so unfortunately abra app upgrade might not be reliable for ensuring that these updates are applied.

Please follow this alternative process, to make sure that these nontraditionally-versioned updates are applied

Using the example of updating a Nextcloud instance, currently running 31.0.6, on cloud.example.com:

  1. Undeploy the app immediately! (Hopefully you did this already 🤞): abra app undeploy cloud.example.com
  2. Consult the table above for whether to "upgrade" or "redeploy"
  3. Check your last deployed version: abra app labels cloud.example.com -- note the upstream app version, the part after the + under "Recipe labels", e.g. in coop-cloud.cloud_example_com.version 12.0.1+31.0.6-fpm, we're looking for 31.0.6-fpm.
  4. If you are at any version below the latest (15.0.0+34.0.5-fpm in our example), you need to upgrade – see subsection below. Otherwise, if you were already on the latest version, and the table below says "redeploy", then deploying the app should get the new version:
  5. abra app deploy cloud.example.com -n
  6. Re-run step #2 of Checking for affected apps.

Applying prerequisite recipe upgrades

  1. Read recipe and upstream release notes to plan a sequence of migrations, e.g. in this case:
    1. From 12.0.1+31.0.6-fpm to 13.2.0+32-fpm
    2. From 13.2.0+32-fpm to 14.6.0+33-fpm
    3. From 14.6.0+33-fpm to 15.0.0+34.0.5-fpm
  2. abra app deploy cloud.example.com
  3. abra app upgrade cloud.example.com; choose the next version in the plan from #1
  4. Wait for the instance to become available again
  5. Run abra app run -u www-data cloud.example.com app -- php occ app:update --all
  6. Repeat steps #3-5 until all updates in the plan are applied
  7. Re-run step #2 of Checking for affected apps.

Automated checking with cc-runall

  1. Download or git clone the cc-runall script
  2. Download jq (either through distribution repositories, or from the same repo)
  3. ./cc-runall wordpress app "php -v"

Forensics

Exploiting these vulnerabilities would likely require multiple attempts. Each attempt has a good chance of crashing the worker it's executed against. This will show up in logs as 500's and 502's.

A successful attack may not leave these traces, so abcence of evidence is not evidence of absence. However, 500 and 502 spikes are evidence of aborant behavior and attacks are one common cause of such behavior.

Upstream Information

PHP Advisory