CuraSec

tag: Cms · 3 items

2026-10-18 · BleepingComputer · source ↗ #drupal#rce#cms
  • Engineer — Plan: Two critical RCE flaws affect all supported Drupal versions with no PoC or KEV yet, but the project itself warns exploitation is imminent — update Drupal core to the patched release this sprint rather than waiting for the next maintenance window.
  • SOC/IR — Skip
  • Leader — Skip
2026-10-15 · The Hacker News · source ↗ #drupal#rce#cms
  • Engineer — Act: If you run Drupal with contributed modules, patch immediately to 11.4.10, 11.3.19, or 10.6.19; at least one unauthenticated exploit path is known. Audit which contributed modules are enabled and prioritize sites with public-facing Field UI exposure.
  • SOC/IR — Learn: No published IOCs or ATT&CK-mapped TTPs in this advisory; monitor for exploitation reports against Drupal-hosted assets and be ready to hunt for web shell drops on CMS servers if active exploitation is confirmed.
  • Leader — Skip
2026-07-12 · BleepingComputer · source ↗ #cms#exploitation#acsc
  • Engineer — Act: If you run WordPress, Drupal, Joomla, or similar CMS with unpatched plugins, audit for compromise indicators and bring all CMS software and plugins to current versions immediately — campaigns like this actively scan for known-vulnerable installs.
  • SOC/IR — Act: Hunt for webshell activity and anomalous outbound connections from CMS-hosting servers; check for recently modified PHP/JS files in web roots and tune SIEM rules for CMS-targeted exploitation behavior.
  • Leader — Plan: Confirm whether your organization or managed service providers host any CMS platforms, and ensure patch status is reviewed this quarter; note that global campaigns of this type frequently precede ransomware or data-theft incidents in affected sectors.