Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
Sichere ProgrammierungRelease Notes for Safari Technology Preview 253(23.09.2026 um 23:46 Uhr)
Sichere ProgrammierungNode 20 is no longer available in GitHub Actions(23.09.2026 um 22:46 Uhr)
Sichere ProgrammierungMore ways to request and configure Copilot code reviews(23.09.2026 um 23:25 Uhr)
Sichere ProgrammierungApache Data Lakehouse Weekly: September 15 to 23, 2026(23.09.2026 um 23:14 Uhr)
Sichere ProgrammierungObservatorio de gastos públicos(23.09.2026 um 23:15 Uhr)
Sichere ProgrammierungRelease Notes for Safari Technology Preview 253(23.09.2026 um 23:46 Uhr)
Sichere ProgrammierungNode 20 is no longer available in GitHub Actions(23.09.2026 um 22:46 Uhr)
Sichere ProgrammierungMore ways to request and configure Copilot code reviews(23.09.2026 um 23:25 Uhr)
Sichere ProgrammierungApache Data Lakehouse Weekly: September 15 to 23, 2026(23.09.2026 um 23:14 Uhr)
Sichere ProgrammierungObservatorio de gastos públicos(23.09.2026 um 23:15 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

Beyond "Update All" — selecting plugins across sites while keeping every safety mechanism on

"A vulnerability in Elementor was just disclosed. Several of the sites I maintain run Elementor. I need to update only Elementor across those sites today." If you maintain WordPress sites for multiple clients, this scenario happens…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

"A vulnerability in Elementor was just disclosed. Several of the sites I maintain run Elementor. I need to update only Elementor across those sites today."



If you maintain WordPress sites for multiple clients, this scenario happens several times a month. Core updates and other plugin updates can wait for the regular maintenance run, but a specific plugin needs to land urgently.



The trouble is that mainstream maintenance tools don't really offer a UI for "a targeted update across multiple sites, with safety mechanisms intact." Here's how that design problem can be solved.






The limits of an industry-standard "Update All"



Most WordPress maintenance tools have an "Update All" button on each site's dashboard.




  • Press it, and every plugin update fires at once

  • If any one of them breaks the site, the industry-standard "Safe Updates" / "Atomic Updates" feature rolls everything back

  • There's no granularity for "update just Elementor" or "across only this subset of sites"



The structural reasons the industry converged on this design are covered in three gaps the WordPress maintenance industry still hasn't solved — the Worker-plugin-over-HTTP-API architecture constrains how fine-grained the operations can be.



The practical result: an agency task like "update only Elementor across these sites" tends to fall back to logging into each site one by one and updating manually.






What was needed was two-axis granularity (site × plugin)



WP Maintenance Manager v1.6.2 solves this with two axes of granularity:





  • Site axis: see, across every managed site, which plugins are due for update


  • Plugin axis: pick the (site × plugin) cells with checkboxes — only those combinations are updated



Instead of an "Update All" button, you get a "update only the combinations you picked" button.






Cross-site dashboard design



Opening "Plugin Updates" from the toolbar triggers an SSH-parallel scan across every managed site, surfacing all plugins that are due for update.



Results are grouped by plugin name:




Elementor — needs update on several sites (4.0.0 → 4.0.8)
☐ siteA.com
☐ siteB.com
☐ siteC.com

Yoast SEO — needs update on several sites (22.0 → 22.1)
☐ ...






At a glance, you can see which plugins are out of date on which sites. Looking at the full list of sites, you can make decisions like "update Elementor everywhere, defer Yoast for another window."



Results are cached in the browser and surface immediately even after restarting the app. The parallel SSH scan completes quickly even with a large fleet, so it's lightweight enough to check casually.






A selective update runs with the same safety mechanisms as regular maintenance



This is the key point. When you press "Update selected plugins," the underlying execution uses exactly the same safety mechanisms as a regular maintenance run:




  • Database backup (taken before any update)

  • One-plugin-at-a-time updates with HTTP checks + automatic pinpoint rollback if something breaks (implementation deep dive)

  • Visual check and summary email



The only difference from a regular maintenance run is that Core / theme / translation updates are skipped. Only the plugin combinations you picked actually run.



The log history and report carry a "selective update" tag, and the names of the targeted plugins are recorded. You can trace back later: "when did we push Elementor across multiple sites last month, and to which sites?" The audit trail is preserved.






Takeaway — granularity changes how operations feel



The simplicity of "Update All" is convenient, but it doesn't fit the realistic need to move only a specific plugin across multiple sites simultaneously.



The combination of cross-site dashboard + selective update + safety mechanisms preserved is what makes "a targeted, safe, multi-site update" actually work. When a single plugin's vulnerability gets disclosed, you can update just the affected sites in one action — safely.



What used to be a binary choice between "update everything" and "do nothing" becomes surgical movement with all the safety nets still on. That shifts where the line falls between emergency response and routine maintenance.

CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
IR-PLAYBOOK-VULN-REMEDIATION
MEDIUM
SOC Incident Playbook: Vulnerability Remediation & Verification
1-Click Detection Engineering: Sigma & YARA Rules
SOC Ready
title: Detect Exploitation - Beyond "Update All" — selecting plugins across sites while keeping every safety mechanism on
id: 75ba09c4-6b15-435d-aec1-0f73ecf10065
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-24
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-24"
        description = "YARA Signature for "
    strings:
        $str = "Beyond \"Update All\" — selectin" ascii wide
    condition:
        any of them
}
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Beyond "Update All" — selecting plugins across sites while keeping every safety mechanism on

Thematisch verwandte Begriffe: Beyond, Update, selecting, plugins · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-96550 | A vulnerability was found in sfturing hosp_order up to 627f426331da8086c…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel TTP ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick