Patching the vulnerability may not be enough for affected Drupal Commerce stores. The Security Team has also instructed operators to check their orders for inconsistencies.
...more
A new CISA deadline raises the urgency of the PHP2Shell response. Specbee's account of emergency Drupal patching shows why deploying fixes and establishing what happened before them are separate challenges.
...more
A patched server may still hold evidence of an earlier intrusion. Amazon's earliest reported PHP2Shell attack attempt occurred four days before public disclosure, raising questions about activity that preceded emergency updates.
...more
A vulnerable module does not always mean an immediately exploitable site. Upload permissions, token usage and configuration settings can determine the actual exposure.
...more
A Composer symlink flaw affects versions that still satisfy Drupal 11's minimum requirement. The fix is available in Composer 2.10.3 and 2.2.30.
...more
PHP branches used by supported Drupal 10 and 11 environments received security fixes, but determining exposure requires more than checking a version number.
...more
The September disclosure turns a pre-announced security release into a broader maintenance task across 16 projects. Exposure varies sharply by configuration, so operators need more than the Critical labels to set priorities.
...more