## Synthesis additions (2026-09-10 — review at the update boundary) - [[3. Resources/Permanent Notes/Trust Granted at Admission Must Be Re-Verified at Every Update]] — WordPress.org now blocks high-risk plugin releases at the update API; the open question is whether trunk-level compromise falls outside a release-triggered gate. # WordPress Hosting Security Stack MOC ## Synthesis additions (2026-10-01 — plugin trust models and AI-generated plugins) - [[3. Resources/Permanent Notes/A Plugin Is Safest When Access Is Declared Approved and Enforced at Runtime]] — A plugin's access is only as trustworthy as the chain of declaration, administrator approval, and runtime enforcement; a design argument drawn from a vendor source (Cloudflare's EmDash post). - [[3. Resources/Readwise/Articles/Lessons Learned From Vibe Coding Plugins]] — WP Minute meetup (auto-captioned): guest Patrick Gallagher of GridPane argues AI tools now produce working plugins but hallucinate, and describes red-teaming a build with two or three other models. ## Synthesis additions (2026-10-01 — WordPress.org update-API data collection) - [[3. Resources/Readwise/Articles/Down the Rabbit Hole - A Look at the WordPress Update API]] — Duane Storey's 2024-11-08 blog post claims update checks to three api.wordpress.org endpoints send more than needed, including headers for every installed plugin and theme; his observations, not independently checked. - [[3. Resources/Readwise/Articles/Exhibit Two to the Declaration of Kaitlin Keohane Filed at Dkt. No. 303-4, Refiled Pursuant to Court Order at Dkt. No. 381]] — Dkt. 419: eight transcript pages of Barry Abrahamson's 2025-12-19 Rule 30(b)(6) deposition for Automattic in WP Engine v. Automattic, covering a crawler site, update checks, and the Mission Control dashboard. - [So Barry Abrahamson's Previously Sealed Testimony in the Automattic Trial...](3.%20Resources/Readwise/Tweets/So%20Barry%20Abrahamson's%20Previously%20Sealed%20Testimony%20in%20the%20Automattic%20Trial....md) — Duane Storey's X thread says Abrahamson's newly public testimony shows Automattic used WordPress.org update-API data; one-sided opinion thread, and the note separates its claims from the Dkt. 419 excerpt. ## Synthesis additions (2026-10-01 — hosting-industry consolidation and alternative platforms) - [[3. Resources/Readwise/Articles/EmDash 1.0 The Stable CMS With a Secure Plugin Registry]] — Cloudflare (a vendor) announces EmDash 1.0, an MIT-licensed Astro CMS with an AT Protocol plugin registry, and says its sandboxed plugins get only declared, admin-approved abilities, unlike WordPress plugins sharing the PHP process. - [[3. Resources/Readwise/Articles/Spacefast Automattic’s New Static Hosting]] — WP Minute Tutorials' 15-minute preview of Automattic's Spacefast static hosting: a landing page, a full-stack to-do app, and a static export of a local WordPress site; prices are the narrator's reading, captions garbled. - [[3. Resources/Readwise/Articles/GoDaddy Jumps on Takeover Report While the Would-Be Buyer's Stock Sinks]] — Weak scope fit (hosting-industry ownership news, not security): 24/7 Wall St. relays an FT report that Gen Digital made a preliminary approach to GoDaddy; Gen fell 12.05%, GoDaddy rose 4.64%, no terms disclosed. ## Synthesis additions (2026-09-26 — the five-hour exploit window) - [[3. Resources/Readwise/Articles/Community + Code Episode 34 - Maciek Palmoski]] — Palmowski (Patchstack) on Community + Code (2026-09-25): exploitation follows disclosure within about five hours and core itself is now a target, so the working controls are auto-update, managed patching and virtual patching, not update cadence; pairs with [[3. Resources/Permanent Notes/A Patch Release Starts an Exploitation Race Not a Grace Period]] ## Synthesis additions (2026-09-05 — incident response / abandoned plugins) - [[3. Resources/Permanent Notes/Restoring a Backup Restores the Entry Point]] — A clean backup reverts the payload of a compromise but leaves the entry point open; restoration without root-cause remediation schedules reinfection. ## Synthesis additions (2026-09-05 — first-party vs third-party vulnerability disclosure norms) - [[3. Resources/Permanent Notes/First-Party Disclosure Asserts Where Third-Party Disclosure Measures]] — Names the disclosure-detail gap between a vendor's own security advisory (Jetpack 16.1.3) and third-party advisories for the same bug class. ## Synthesis additions (2026-09-05 — redundancy and coordination failure surfaces) - [[3. Resources/Permanent Notes/Redundancy That Requires Coordination Is a New Failure Surface]] — names a distinct failure mode from correlated-cause redundancy failure — coordination between redundant workers can itself produce the outage, relevant to any multi-region or multi-instance hosting claim. ## Synthesis additions (2026-09-05 — vendor trust and disclosure incentives) - [[3. Resources/Permanent Notes/Selecting Vendors on Clean Breach Records Rewards Non-Disclosure]] — treating a vendor's clean breach record as a primary purchase signal rewards silence over honest disclosure, since the two look identical from outside ## Synthesis additions (2026-09-05 — second-order injection / sink-level review) - [[3. Resources/Permanent Notes/Escaping at Entry Does Not Protect a Later Re-Parse at the Point of Use]] — CVE-2026-19949 (All-in-One WP Migration, 5M+ installs): entry-time escaping held, but the plugin's own restore rewrite re-parsed stored trackback content into SQL — a textbook second-order injection audit checklists should test for. ## Synthesis additions (2026-09-05 — patch adoption vs patch speed) - [[3. Resources/Permanent Notes/A Patched Vulnerability Still Exposes Whoever Has Not Updated]] — A five-day vendor fix left 65% of a 5M+ install base still exposed two weeks later — ecosystem exposure tracks adoption, not maintainer response time. ## Synthesis additions (2026-09-05 — second-order SQLi / credential lifecycle) - [[3. Resources/Permanent Notes/A Defensive Measure That Preserves a Secret Across an Operation Makes It Reachable During It]] — a preserved secret's restoration checkpoint is also its exposure window, illustrated by the AI1WM trackback-to-RCE chain ## Synthesis additions (2026-09-05 — relocating a control past a resistant user) - [[3. Resources/Permanent Notes/Relocate the Control When the User Won't Adopt It]] — Cloudflare Zero Trust in front of login pages converts unwinnable 2FA persuasion into an architecture decision the agency controls ## Synthesis additions (2026-09-05 — in-process controls fail when the system they protect is compromised) - [[3. Resources/Permanent Notes/A Control Inside the System It Protects Falls With It]] — A control running inside the system it protects can be disabled by whoever compromises it — from a vendor's own security-plugin guide. ## Synthesis additions (2026-09-05 — backup and recovery discipline) - [[3. Resources/Permanent Notes/An Untested Recovery Path Is an Assumption Not a Capability]] — A backup nobody has restored is an assumption, not a capability — the one item on every backup checklist that gets skipped. ## Synthesis additions (2026-09-05 — consent must gate the action, not just describe it) - [[3. Resources/Permanent Notes/Consent Is a Gate Not a Notice]] — A non-blocking Terms & Conditions box is documentation, not consent — the enforceable distinction behind the Rank Math Application Password incident. ## Synthesis additions (2026-09-05 — detection vs. triage capacity) - [[3. Resources/Permanent Notes/A Detector That Outruns Its Triage Queue Enlarges the Backlog Not Safety]] — the Core Security Initiative's own two pillars (AI scanning, backlog clearing) pulling against each other ## Synthesis additions (2026-09-04 — who audits the auditor) - [[3. Resources/Permanent Notes/An Exemption Granted by Confidence Rather Than Audit Voids the Regime Around It]] — the proposed answer to the Rank Math credential grab is mandatory infrastructure audits for admin-level plugins, announced with a self-exemption in the same message; the control the stack actually gains depends on whether the exemption is auditable. ## Synthesis additions (2026-08-31 — patch reach) - [[3. Resources/Permanent Notes/Patch Coverage Is a Distribution Problem Not a Code Problem]] — Pods backported five fixes across seven branches to WP 4.5 and still stranded 2.0–2.6; hosts are the only actor positioned to close a branch-floor gap, by inventorying versions rather than relying on user action. ## Synthesis additions (2026-08-30 — AI-era disclosure volume + credential delegation) - [[3. Resources/Permanent Notes/A Backlog Target of Zero Is Incoherent When Discovery Is Being Automated]] — WordPress's own Core Security Initiative commits to driving open findings to zero while adding AI-assisted scanning; the two pillars pull against each other and the post never reconciles them. - [[3. Resources/Permanent Notes/Development Dependencies Shipped to Production Are Exploit Primitives]] — Patchstack's root-cause note on the GiveWP CVSS 10.0 — an unpruned vendor directory is a gadget-chain surface, which makes a build flag a security control. - [[3. Resources/Permanent Notes/A Precondition That Describes Normal Operation Is Not a Mitigation]] — GiveWP's stated trigger, one published donation form and one active gateway, is the plugin working as intended; read every precondition against deployment reality. - [[3. Resources/Permanent Notes/A Credential That Cannot Be Scoped Forces Every Delegation to Be Total]] — WordPress Application Passwords have no capability scopes, so any plugin shipping an AI agent must take full admin or nothing — the Rank Math 1.0.277 case. ## Synthesis additions (2026-08-24 — backlog gap-fill (second pass)) - [[3. Resources/Permanent Notes/Edition-Agnostic Protection and Edition-Aware Alerting Fail Independently]] — a shared plugin slug across seven editions breaks version-keyed alerting while behaviour-keyed blocking keeps working. - [[3. Resources/Permanent Notes/AI-Assisted Vulnerability Discovery Is Not Uniform Across Finders]] — applies to how disclosure windows get argued for WordPress plugin vulnerabilities. ## Synthesis additions (2026-08-11 — application-aware hosting) - [[3. Resources/Permanent Notes/Generic Hosting Security Cannot See WordPress-Specific Attack Semantics]] — distinguishes generic server hardening from controls that understand WordPress routes, capabilities, and plugin behavior. ## Synthesis additions (2026-08-11 — patch-to-exploit response) - [[3. Resources/Permanent Notes/Patch-to-Exploit Speed Makes Route-Aware Detection Part of Patching]] — joins rapid updates with request-body-aware detection and post-update compromise checks. ## Synthesis additions (2026-08-11 — consent and release evidence) - [[3. Resources/Permanent Notes/A Privileged Setup Flow Needs Explicit Consent at Every Trust-Boundary Crossing]] — treats privileged onboarding as an authorization boundary even when the vendor's purpose is benign. - [[3. Resources/Permanent Notes/Release Downloads Measure Channel Following Not Active Adoption]] — distinguishes privacy-preserving release-channel evidence from active-install telemetry. A map of the managed-WordPress hosting market's security positioning as of May 2026, organized by layer — the threat surface AI API keys introduce, the architectural gaps in WordPress core that can't safely close them, and the divergent vendor responses (third-party-attested vs. default-on convenience). ## Core Question In a WordPress ecosystem where WP 7.0 ships first-class AI integration but core has no native secure-secret storage, what does "secure hosting" actually mean — and how do customers tell certified-secure providers apart from default-on-AI providers without reading the configuration? --- ## The Threat Layer ### Patchstack 2026 data + Oliver Sild's economic argument - [[3. Resources/Readwise/Articles/Patchstack CEO Warns WordPress 7.0 Could Trigger “Absolute Rush” To Steal AI API Keys]] — Two interlocking claims: - **Economic shift**: AI API keys are a fundamentally higher-value target than historic WP credentials. Previous attacks gave hackers server resources (phishing pages, spam, redirect traffic, botnets); AI keys let attackers **spend the victim's money directly** on token-max'd vulnerability research, model abuse, etc. - **Scale data**: 11,334 new vulnerabilities in the WP ecosystem in 2025 (+42% YoY), exploitation typically within **5 hours** of disclosure, 70-90% of hosted sites have at least one known vulnerability per Patchstack's hosting-provider scans. ### The architectural gap - WP Security Team's John Blackbourn (in same article): WordPress has **no native two-way encryption** for stored secrets that survives key rotation or site migration. Current state requires tying encryption to `wp-config.php`, which breaks the moment the key rotates or the site moves environments. Blackbourn's proposed encryption API is still hypothetical. - This means: any plugin or core module storing AI API keys in 2026 is storing them in a layer the WP Security Team has publicly admitted can't be safely encrypted. --- - [[3. Resources/Permanent Notes/Trunk and Tagged Stable Zip Are Separate Attack Surfaces]] — a malicious trunk commit is live risk for source-pullers and zero risk for install-and-update users until tagged. ## The Response Layer (Third-Party Attestation) ### Secure Hosting Alliance certification - [[3. Resources/Readwise/Articles/Secure Hosting Alliance Certification WordPress VIP-2|Secure Hosting Alliance Certification WordPress VIP]] — WordPress VIP joins the inaugural SHA cohort. Pitch: - SHA is an **independent benchmark** for security and operational rigor — third-party-attested, not self-reported - Stacks alongside **SOC 2** and **FedRAMP** as part of an "independently verifiable" compliance posture - Framed as **industry coordination**, not a single-vendor badge — initial cohort of providers with shared commitment ### Who VIP is positioning against (implicitly) WP VIP is Automattic's enterprise arm. The SHA pitch lands directly in a market where: - Patchstack data names a credible threat (above) - Competitors are shipping AI integration without third-party attestation (below) - The WP Security Team has acknowledged the architectural gap (above) --- - [[3. Resources/Permanent Notes/A Readme-Only Commit Can Register as a Release]] — a release-mechanics change that affects every plugin author's workflow, unverified against my own plugins as of 2026-09-11. - [[3. Resources/Permanent Notes/An SVN Commit Succeeding Is Not Users Receiving the Update]] — distribution now waits on a cooldown plus a Jetpack Scan verdict the author cannot see in advance — budget it into security releases. ## The Failure Mode Layer (Default-On Without Attestation) ### SiteGround's WP 7.0 AI Connector activation - [[3. Resources/Readwise/Articles/SiteGround's Icky Approach to AI in WordPress 7.0 - Rhys Wynne]] — Rhys Wynne's first-person account: - SiteGround activated their AI Studio + AI Agent as the **default AI connector** in customers' wp-admin during the WP 7.0 auto-update - Notification was a **midday-Friday email** customers easily skim past - Activation UI placed **at the bottom of wp-admin** (deliberate choice — most plugins fight for top-of-page real estate) - Customers are **paying £500+/year** to SiteGround for hosting; Wynne's argument is that paid customers shouldn't be the product - "Switch it on and hope people don't notice or kick up a fuss" framed as the modus operandi of the broader AI rollout ### Independent corroboration (added 2026-05-31) - [[3. Resources/Readwise/Articles/SiteGround Faces Backlash After Automatically Installing AI Plugin On Customer Sites]] — wp-content.co's reporting; multiple named-customer testimony (Domenico Longo, Tony Gale, Maarten Belmans / Wombat Plugins); CORS issue reports affecting WooCommerce sites; documents the 850k-sites × 2-plugin-updates = 1.7M downloads/week scale (Steve Burge data point) - [[3. Resources/Readwise/Articles/SiteGround Auto-Installs AI Plugin on Customer Sites, Calls WordPress 7.0 a ‘Watershed Moment’ as Customers Push Back]] — adjacent reporting on the same incident - [[3. Resources/Readwise/Snipd/Data/WP Tavern/_218 – Luke Carbis on the Future of WordPress Plugins_ AI, Ethics, and New Directory Standards]] — Luke Carbis with Nathan Wrigley (May 2026); 4× increase in plugin submissions over 12 months driven by AI; week-long review wait time; active-installs ranking dynamic that compounds default-on activation into algorithmic incumbent advantage ### Where this meets the threat layer SiteGround's AI Connector stores customer API keys in exactly the layer Blackbourn says can't be safely encrypted, default-on, on paying customer infrastructure, with no SHA / SOC 2 / FedRAMP independent attestation cited. --- - [[3. Resources/Permanent Notes/Scanner Scope Needs the Execution Path Stated Not Just the File Type]] — a PHP-page-load scanner says nothing about a payload that runs during a Node build step. ## Cross-Cutting Patterns ### Default-on vs opt-in | Pattern | Default-on (SiteGround) | Opt-in / human-gated | |---|---|---| | User awareness | Activated silently in update | Customer approves remediation plan (GoDaddy AI Troubleshooter pattern) | | Credential exposure | Stored in wp-config layer | Gateway-injected at request time (Claw Patrol pattern) | | Verification | Self-attested feature shipping | Third-party attested (SHA, SOC 2, FedRAMP) | | Failure mode if breached | Attacker spends customer's AI tokens | Gateway blocks unauthorized request | ### Credential storage pattern The Blackbourn architectural admission means the **credential storage question** generalizes beyond SiteGround: - Where do hosting providers store the AI API keys they're inserting into customer sites? - What happens to those keys on key rotation, environment migration, or hosting transfer? - Is the storage layer independently audited as part of the provider's compliance posture? These questions are now answerable for VIP (yes, audited via SOC 2/FedRAMP/SHA) and unanswered for SiteGround (no third-party attestation cited in the article). --- ## Related MOCs and Notes - [[AI Agent Safety MOC]] — adjacent infrastructure-layer security patterns (Claw Patrol gateway, GoDaddy Troubleshooter backup-verify-rollback) - [[Open Source Governance MOC]] — the WordPress Saga thread under which this hosting-security-tier subthread sits - [[Commons & Community Governance MOC]] — security infrastructure as part of the commons WordPress hosting providers extract from and contribute to --- ## Synthesis additions (2026-07-05) From synthesis-pass 2026-07-05 (batch 3–resonance-filtered Permanents): - [[3. Resources/Permanent Notes/Perm · WordPress security is now a supply-chain + dependency risk, not just plugin reviews]] — review ≠ safety; runtime defense mandatory; threat model: plugins compromised until proven otherwise - [[3. Resources/Permanent Notes/Perm · WordPress plugin ecosystem is a supply-chain target for long-term backdoor campaigns]] — 13-year multi-plugin backdoors; automated updates flow without re-scrutiny; ecosystem is target infrastructure - [[3. Resources/Permanent Notes/Perm · BitNinja + PhantomGuard represent the shift to runtime detection as primary defense]] — prevention-first has failed; runtime detection (behavior, honeypots, anomaly) is now primary; WAF mandatory --- ## Open Questions - Will the SHA cohort grow beyond the inaugural list, and which providers won't join (and why)? - How much does default-on AI activation contribute to the [[3. Resources/Readwise/Articles/WordPress Market Share Declines For Six Months In A Row|six-month market share decline]] vs. the broader leadership/PE saga? - If WordPress core adds the two-way encryption API Blackbourn proposed, does it materially close the threat surface, or does the storage gap re-emerge at the hosting layer regardless? - What's the analog of SHA in non-WordPress CMS / SaaS markets — is there a Shopify Secure Hosting equivalent? If not, why has WordPress generated one first? --- ## Related Threads to Develop - ✅ **Wynne ↔ Blackbourn cross-reference** synthesized 2026-05-28 as [[3. Resources/Permanent Notes/WordPress Stores AI API Keys in a Layer Its Own Security Team Says It Cannot Encrypt]] - ✅ **Active-installs ranking dynamic** synthesized 2026-05-31 as [[3. Resources/Permanent Notes/Active Installs Reward Existing Winners]] — names the algorithmic-incumbency mechanism by which default-on activation compounds into discoverability moat; Luke Carbis #218 as primary source - ✅ **Supply-chain / actor-tracking layer** synthesized 2026-06-05 as [[3. Resources/Permanent Notes/Supply-Chain Defense Tracks Bad Actors Not Bad Code]] — the threat layer above CVEs: hijacked update channels and acquired plugins where the code isn't broken, the actor is; the "Protect The Shire" 24-hour release cooldown as the platform-level actor-vetting response; Ginder/WP Beacon + GoDaddy Steam-C2 as primary sources - **Market-share decline causation**: the SEJ piece names trust erosion as a contributor to decline; the Patchstack data + SiteGround behavior pattern suggests a separate-but-related security-trust erosion. Whether these are the same trust problem or two trust problems is testable. ## Synthesis additions (2026-06-11) From the 3-day Readwise review — new atoms wired in: - [[3. Resources/Permanent Notes/General WordPress-to-WordPress Sync Is Unsolvable Because Environment Is Part of the Site]] — site = DB + files + environment; environment-as-state is why generic sync terminates in human judgment ## Connected Literature Notes (synthesis sweep 2026-07-14) - [[3. Resources/Literature Notes/Lit · WordPress site sync is unsolvable in general]] — the Literature-note source for the sync permanent above - [[3. Resources/Literature Notes/Lit · wpm WordPress package manager]] — a package-manager approach to the same environment-as-state problem sync can't solve generically ## Connected Literature Notes (synthesis 2026-06-17) - [[A Field Guide to Threat Vectors in the Software Supply Chain]] — the supply-chain threat layer of the hosting security stack - [[Announcing GUAC, a great pairing with SLSA (and SBOM)!]] — supply-chain visibility tooling layer (backfill 2026-06-18) ## Permanent Notes (synthesis 2026-06-26 gap-fill) - [[3. Resources/Permanent Notes/An Open Marketplace Turns Extensibility Into Liability Without an Owned Security Layer]] — Ferriman: WP's plugin ecosystem is its strength AND largest attack surface; without an owned, funded security-review layer, extensibility becomes liability — sharpened by AI compressing the exploit window to ~5 hours. The governance frame above [[3. Resources/Permanent Notes/Supply-Chain Defense Tracks Bad Actors Not Bad Code]] ## Permanent Notes (synthesis 2026-06-27 gap-fill) - [[3. Resources/Permanent Notes/Emulated Local Dev Trades Production Fidelity for Zero-Setup Speed]] — WordPress Studio cluster (independent reviews): WASM/SQLite local dev buys instant setup by approximating production, and the fidelity gap (no DB queries, Playground divergence) is unpredictable — you can't know at spin-up which build hits it. The emulation-side complement to [[3. Resources/Permanent Notes/General WordPress-to-WordPress Sync Is Unsolvable Because Environment Is Part of the Site]] ## Connected Literature Notes (synthesis 2026-07-18 — 20-doc batch) - [[3. Resources/Literature Notes/Unauthenticated SQL Injection in WordPress Core Fixed in 7.0.2]] — Patchstack's teardown of the 7.0.2 SQLi: is_array() type-confusion + REST batch-route confusion; the technical anatomy under the release - [[3. Resources/Literature Notes/WordPress 7.0.2 Patches Rare Pre-Authentication RCE as Hosts, CDNs Get 24-Hour Head Start]] — The Repository's coverage: 24h embargoed host/CDN WAF collaboration; object-cache precondition; live exploitation observed - [[3. Resources/Literature Notes/My AI Security Pipeline for WordPress Plugins]] — Ginder's four-step audit→prove→submit→redirect pipeline; source of the [[Auditing the Build Not the Install Is What Makes Personal-Scale Coverage Possible]] permanent - [[3. Resources/Literature Notes/The Hosting Price Squeeze, Part 1 Why Your Costs Keep Climbing]] — cPanel +300% under PE rollup, VMware/Broadcom reset; hosting-tooling economics as the cost side of the managed-WP stack ## Permanent promoted (synthesis 2026-07-18) - [[3. Resources/Permanent Notes/Sanitize by Value Not by Input Type]] — from the 7.0.2 SQLi teardown: type is not a trust boundary; a sanitizer gated on `is_array()` is bypassed by sending the input as a string. Normalize first, then sanitize unconditionally. ## Permanent Notes (synthesis 2026-07-21 gap-fill) - [[3. Resources/Permanent Notes/Request-Local Caches Are Security Boundaries]] — the wp2shell chain shows how attacker-shaped query results become trusted request state before a sparse update carries them into durable storage - [[3. Resources/Permanent Notes/Temporary Privilege Changes Require Re-Entrancy Guards]] — nested REST dispatch observes the Customizer's borrowed administrator identity, turning shared runtime state into an authorization bypass - [[3. Resources/Permanent Notes/AI Finds Exploit Chains Faster Than Humans Can Audit Them]] — the discovery account shifts the WordPress zero-day bottleneck from search cost to human reproduction, explanation, and coordinated disclosure ## Permanent Notes (synthesis 2026-07-21 — run 2) - [[3. Resources/Permanent Notes/Zet · Rapid weaponization outpaces manual update workflows]] — migrated with the Akrites evidence: automated discovery creates an attacker window wherever remediation remains bounded by human review speed - [[3. Resources/Permanent Notes/Update Signatures Prove Provenance Not Freshness]] — signatures authenticate the builder, while a version ratchet prevents replay of an older validly signed vulnerable release - [[3. Resources/Permanent Notes/WordPress's Compatibility-First Culture Is Now Its Binding Security Constraint]] — the cluster-level thesis: once AI democratizes discovery, the limiting factor is shipping fixes the ecosystem accepts, and backward-compat (what makes plugins a business) is the blocker. Ties the wp2shell attacker/defender/mitigation/governance docs (Kues, Wordfence, pattonwebz signed-updates, the r/ProWordPress open letter, Akrites) into the security-as-core-feature fight ## Connected Literature Notes (synthesis 2026-07-21 — run 8) - [[3. Resources/Literature Notes/Shared Responsibility Model - Amazon Web Services (AWS)]] — separates provider-controlled infrastructure from customer-controlled configuration and workload security - [[3. Resources/Permanent Notes/Perm · WordPress security is now a supply-chain + dependency risk, not just plugin reviews]] — reframes WordPress security around dependency provenance and distribution rather than isolated review of plugin code ## Connected Literature Notes (synthesis 2026-07-21 — run 11) - [[3. Resources/Literature Notes/WordPress for Enterprise - Platform Security]] — places enterprise platform-security claims inside the shared-responsibility and evidence-based evaluation stack ## Connected Permanent Notes (synthesis 2026-07-21 — run 19) - [[3. Resources/Permanent Notes/Perm · BitNinja + PhantomGuard represent the shift to runtime detection as primary defense]] — treats behavioral detection, honeypots, and fast containment as the primary layer once installation-time prevention can't be trusted - [[3. Resources/Permanent Notes/Perm · AI-powered content + design inside the editor closes the friction loop for user-generated velocity]] — brings generation into the WordPress editing surface, expanding the product layer whose permissions, keys, and generated output hosts must govern - [[3. Resources/Permanent Notes/Perm · Vibecoding bypasses CMS entirely, draining relative share to 'None']] — names the AI-built no-CMS path that changes the market and operating context for WordPress hosts - [[3. Resources/Permanent Notes/Perm · WordPress plugin ecosystem is a supply-chain target for long-term backdoor campaigns]] — treats trusted plugin distribution and delayed malicious activation as a supply-chain threat that survives ordinary point-in-time review ## Connected Permanent Notes (synthesis 2026-07-21 — run 25) - [[3. Resources/Permanent Notes/Zet · Infra-only defences miss most WordPress attacks]] — uses the reported 26 percent block rate to show why infrastructure controls need application-aware detection and patching layers - [[3. Resources/Permanent Notes/Zet · Password manager adoption essential for security]] — treats unique managed credentials as a baseline control independent of which audited password-manager product a team selects ## Synthesis additions (2026-07-22) - [[3. Resources/Permanent Notes/Client-Side Processing Does Not Move the Server Trust Boundary]] — keeps server-side validation in place when browser-side media processing reduces host CPU and memory work. ## Synthesis additions (2026-07-27) **Cross-link — the maintenance-is-security-capacity thesis** - [[3. Resources/Permanent Notes/Cheap Generation Raises the Total Maintenance Bill]] — the security corollary of this cluster: on a large install base, maintenance capacity *is* vulnerability-surface capacity ("caution scales with the install base"). wp2shell is the extreme case — one core bug, millions of sites — where cheap generation's maintenance debt becomes a security debt. ## Synthesis additions (2026-07-30) - [[3. Resources/Permanent Notes/A Safety Control That Cannot See Severity Becomes a Hazard]] — Protect The Shire measured: CVE fixes and cosmetic releases held for identical durations (24.4h, then 6.8h), while the fix went public and downloadable during the hold. The actor-vetting rationale is sound; the severity-blindness is the defect, and the fix is automatic CVE-keyed expedition rather than a shorter uniform gate. - [[3. Resources/Permanent Notes/Validation That Inspects Steps Cannot See Composition]] — generalizes the wp2shell batch-endpoint desync into a reusable architectural rule, and shows the same failure recurring in LLM safety filtering. ## Synthesis additions (2026-08-01, run 3–4) - [[3. Resources/Permanent Notes/Point-in-Time Review Cannot Detect an Attack That Unfolds Over Time]] — "the repository is a snapshot, the attack is a movie." Four of the six documented WordPress.org supply-chain vectors are defined by *when* they happen and present clean at review time by construction, which is how one campaign ran 13 years across 44 plugins. - [[3. Resources/Permanent Notes/AI Adoption Concentrates Where It Is Pleasant Not Where the Pain Is]] — the operational reason platform-level controls beat agency-level habit change: 45% of agencies running 100+ sites still patch by hand, and maintenance is the least-automated use of AI they report. ## Synthesis additions (2026-08-07) - [[3. Resources/Permanent Notes/A Parser Disagreement Between Two Sanitizers Is the Exploitable Seam]] — CVE-2026-64638 ("XSS2Shell"), a pre-auth core XSS affecting all WordPress versions: `wp_strip_all_tags()` and `wp_kses_post()` disagree about the same failed-login username value, and the seam between two trusted, individually-correct sanitizers is the vulnerability. Patched 7.0.3. The demonstrated PHP-execution escalation (via Application Passwords, one admin click) is conditional and was only proven on a clean local install, not production — the article models unusually careful evidence scoping worth citing as a standard. ## Synthesis additions (2026-08-08) - [[3. Resources/Permanent Notes/Zet · CSS-only carousel solutions improve performance]] — orphan fix, MOC registration only (the note's own outbound link here was already correct; the MOC side of it was missing). Performance and delivery defaults sit alongside the security stack as platform-level properties a site owner does not choose individually. ## Synthesis additions (2026-08-11, reconciliation) - [[3. Resources/Literature Notes/Lit · WordPress scales with proper architecture]] — connects enterprise governance, migration risk, caching, and reusable block-theme patterns to the operational hosting stack. ## Synthesis additions (2026-08-11, OSS security backlog) - [Awesome Motive CDN Breach Hits 1.2 Million Sites Running OptinMonster](https://read.readwise.io/read/01kv89q0w6xf3cprpw7nf60scj) — shows an upstream CDN credential compromise multiplying through trusted plugin delivery and an authenticated administrator browser session; the Markdown link avoids the source filename's nested brackets breaking Obsidian wikilink parsing. - [[3. Resources/Readwise/Articles/From a 7 KB file to a 13-year backdoor operation]] — supplies the persistence mechanics behind the existing point-in-time-review and long-term plugin-campaign Permanents. - [[3. Resources/Permanent Notes/Perm · BitNinja + PhantomGuard represent the shift to runtime detection as primary defense]] — captures the BitNinja interview's durable claim that runtime monitoring becomes primary once installation-time prevention can't be assumed to hold. ## Synthesis additions (2026-08-11, provenance coverage) - [[3. Resources/Readwise/Articles/Developer Traces 13-Year Backdoor Campaign Across 44 WordPress.org Plugins to a Single Operator]] — external coverage of the campaign reinforces the existing continuous-review and publisher-provenance claims without creating another overlapping Permanent. ## Synthesis additions (2026-08-11, WordPress platform evidence) - [[3. Resources/Permanent Notes/A Platform Label Cannot Substitute for a Performance Diagnosis]] — replaces platform reputation with measurement of the server, database, cache, payload, browser, and extension work actually consuming time. - [You Don't Have to Leave WordPress to Work With AI](https://read.readwise.io/read/01kvv219sr8chbzfv80j3hfv26) — thin event page retained for its locked-down structured-tool framing, not promoted as independent security evidence. - [[3. Resources/Readwise/Articles/WordPress.com Review]] — external review evidence on the hosted product's editor framing and observed uptime, kept distinct from WordPress.org platform claims. ## Synthesis additions (2026-08-11, hosting backlog) - [[3. Resources/Readwise/Articles/One Month of EmDash Hosting Here’s What We’ve Sorted]] — vendor operations note retained for Astro routing, development-bypass hardening, Nginx media handling, and managed WordPress hosting implementation details. - [[3. Resources/Readwise/Articles/The Enterprise WordPress Playbook]] — vendor guide retained for its explicit open-platform tradeoff: licensing cost shifts into engineering, governance, and operations rather than disappearing. ## Synthesis connections (2026-08-11, carryover reconciliation) - [[3. Resources/Readwise/Podcasts/How Can Hosts Communicate Security Risks Without Creating Fear (with Aaron Campbell)]] — host communication should turn risk into concrete retrievable action rather than fear. ## Synthesis additions (2026-08-16, wp2shell cluster — coordination, aftermath, technical threads) - [[3. Resources/Literature Notes/wp2shell — Pre-Auth WordPress Core RCE Chain (Icex0 PoC)]] — full deep-read of the chain itself - [[3. Resources/Permanent Notes/First-Principles Source Reading Finds Bugs Patch-Diffing Hides]] — reading source from first principles surfaces bugs that diffing against a known patch hides; the batch-endpoint desync claim from this same source was linked instead of duplicated (see Batch Endpoint Validate-Execute Desync Is an Exploitable Seam, below) - [[3. Resources/Literature Notes/How Two WordPress Core Bugs Chained into Pre-Auth RCE]] — gap-filled literature note for two existing Permanents (Temporary Privilege Changes Require Re-Entrancy Guards; Request-Local Caches Are Security Boundaries) - [[3. Resources/Permanent Notes/Checksum Verification Closes the Gap Auto-Update Status Leaves Open]] — an update-status flag proves a version shipped, not that the running files match it - [[3. Resources/Literature Notes/Exploit Brokers Pay $500,000 for a WordPress RCE]] — links existing AI Finds Exploit Chains Faster Than Humans Can Audit Them (same source, prior pass) - [[3. Resources/Permanent Notes/Batch Endpoint Validate-Execute Desync Is an Exploitable Seam]] — a REST batch endpoint that validates one array and executes another creates an exploitable desync - [[3. Resources/Literature Notes/WP2Shell WordPress Exploit Technical Analysis and Real Attack Data (Wordfence)]] — Wordfence's technical/attack-data angle, distinct from the vault's other wp2shell literature notes - [[3. Resources/Permanent Notes/Attack Volume Is Not Evidence of Harm]] — high probe counts measure attacker interest, not successful compromise - [[3. Resources/Literature Notes/How Signed Updates Work]] — companion to the existing Update Signatures Prove Provenance Not Freshness (same source) - [[3. Resources/Permanent Notes/Signing Narrows Trust to the Build System, It Doesn't Eliminate It]] — signing relocates the trust question to the build pipeline rather than removing it - [[3. Resources/Literature Notes/wp2shell Aftermath (Wordfence)]] — the timeline/aftermath angle, distinct from the vault's technical-analysis and coordination wp2shell notes - [[3. Resources/Permanent Notes/A Patch Release Starts an Exploitation Race Not a Grace Period]] — extends Update Signatures Prove Provenance Not Freshness - [[3. Resources/Literature Notes/WP2Shell Coordination Was Part of the Protection]] — coordinated host/CDN response as part of the mitigation, not just the patch - [[3. Resources/Permanent Notes/Security Coordination Is Infrastructure That Degrades Without Maintenance]] — extends Zet · Infra-only defences miss most WordPress attacks - [[3. Resources/Literature Notes/Ninety minutes watching attackers weaponize the WordPress core RCE]] — same source as the existing Patch-to-Exploit Speed Makes Route-Aware Detection Part of Patching, which already covers the 90-minute timeline/URL-only-rule claim - [[3. Resources/Permanent Notes/Normalized Behavior Detection Outlasts Payload Signatures]] — behavior-normalized detection rules survive payload mutation that signature rules don't - [[3. Resources/Literature Notes/An Open Letter to WordPress.org It's Time to Make Security a Core Feature]] — cross-references the existing WordPress's Compatibility-First Culture Is Now Its Binding Security Constraint, which already sources this article ## Synthesis additions (2026-08-16, Secure Hosting Alliance and hosting-security evaluation) - [[3. Resources/Literature Notes/227 – Maciek Palmowski on Testing Secure WordPress Hosting]] — testing methodology for secure-hosting claims - [[3. Resources/Permanent Notes/Security Controls Are Configurations Not Purchases]] — a host's security posture is a set of configuration choices, not a line of purchased products ## Synthesis additions (2026-08-16, patch-response and dependency-delay threads) - [[3. Resources/Literature Notes/The WordPress update button isn't telling the truth anymore]] — links the existing P1 from this same origin doc, A Safety Control That Cannot See Severity Becomes a Hazard - [[3. Resources/Permanent Notes/Tooling Cannot Be Faster Than the API It Polls]] — an update-checker's responsiveness is capped by the freshness of the API it polls - [[3. Resources/Literature Notes/A 7-day Cooldown on Every Dependency]] — sibling Trail of Bits clip to A Safety Control That Cannot See Severity Becomes a Hazard (Protect The Shire) - [[3. Resources/Permanent Notes/A Uniform Dependency Delay Buys Detection Time and Sells Patch Speed]] — the same fixed hold is protective for the ecosystem and costly for the individual, depending on which side of the gate you're on - [[3. Resources/Literature Notes/Protect the Shire Solves One Problem, but Risks Making Another Worse]] — Patchstack has a commercial interest here, flagged as a lingering question; extends Supply-Chain Defense Tracks Bad Actors Not Bad Code and A Single Discretionary Update Channel Is a Security Dependency - [[3. Resources/Permanent Notes/A Release Policy Should Separate Code-Integrity Risk From Patch-Delivery Urgency]] — actor-vetting delay and CVE-patch urgency are different risks and warrant different gates - [[3. Resources/Literature Notes/Critical WordPress vulnerabilities update now, Poland warns]] — secondary security reporting with an unverified version-claim gap flagged in the note itself - [[3. Resources/Permanent Notes/Secondary Security Reporting Is a Triage Trigger Not a Citation]] — a government/press security advisory should prompt verification, not stand as the citation itself ## Synthesis additions (2026-08-16, supply-chain provenance and AI-era detection) - [[3. Resources/Literature Notes/From a 7 KB File to a 13-Year Backdoor Operation]] — literature-note port; the general plugin-ecosystem-as-supply-chain-target claim was already covered by two existing Permanents (2026-07-05), so only the distinct DNS-pivot attribution claim was promoted - [[3. Resources/Permanent Notes/A DNS Pivot Beats Hours of Code Deobfuscation for Attribution]] — a shared DNS/infrastructure fingerprint can attribute an actor faster than deobfuscating their code - [[3. Resources/Literature Notes/SBOMit - Making SBOMs Accurate With Attestations]] — attestation-backed SBOMs, alongside the vault's A Field Guide to Threat Vectors in the Software Supply Chain and GUAC notes - [[3. Resources/Permanent Notes/More Detections Are Not the Same Claim as More Accurate]] — a build tool that finds more dependencies is not thereby more correct about them - [[3. Resources/Literature Notes/Mark Bacsko (BitNinja-PhantomGuard) on WordPress Security, AI Malware]] — vendor-pitch WordPress-funnel thesis logged as a lingering question (rests on one anecdote), not promoted - [[3. Resources/Permanent Notes/Detection Quality Is Downstream of Network Participation Not Model Cleverness]] — a detector's edge comes from the traffic/threat data it sees, not primarily from model sophistication - [[3. Resources/Literature Notes/How Is AI Changing the Security Arms Race (with Aaron Campbell)]] — AI compresses vulnerability-to-exploitation time - [[3. Resources/Permanent Notes/Disclosed Automated Security Action Builds More Trust]] — a host that discloses what its automated defenses did earns more trust than one that acts silently - [[3. Resources/Literature Notes/New WordPress Pre-Auth XSS Could Lead to PHP Code Execution]] — links the existing A Parser Disagreement Between Two Sanitizers Is the Exploitable Seam (same root cause, XSS2Shell) - [[3. Resources/Permanent Notes/Evidence Scope and Vulnerability Scope Are Different Claims]] — a proof-of-concept's demonstrated conditions don't bound how broadly the underlying vulnerability applies - [[3. Resources/Literature Notes/WordPress 7.1 RC, 7.0.3 Security Release, Block Runner, New Playground UI]] — release-week digest covering the 7.0.3 security release; no Permanent forced pending verification of its two citable data points ## Synthesis additions (2026-08-16, ecosystem/maintenance and release-hygiene notes) - [[3. Resources/Literature Notes/WP Weekly 295 – Back]] — ecosystem-news digest - [[3. Resources/Permanent Notes/A Timed Review Window Trades Update Speed for Supply-Chain Safety]] — a fixed review window before auto-applying an update trades speed for a supply-chain safety margin - [[3. Resources/Literature Notes/Plugin Security Will Sink WordPress]] — links the existing An Open Marketplace Turns Extensibility Into Liability Without an Owned Security Layer, which already sources this exact article - [[3. Resources/Literature Notes/WordPress 7.0.1 Fixes Registration Spam, wp_kses() CSS Corruption, and 7.0 Admin Design Glitches]] — cross-referenced to the thinner wordpress.org announcement covering the same release - [[3. Resources/Permanent Notes/A Maintenance Release Earns Fast-Update Trust by Fixing Only Not Adding]] — a release that only fixes and adds nothing earns the fast-update trust a feature release can't - [[3. Resources/Literature Notes/WordPress 7.0.1 Now Available, Fixes 31 Bugs]] — flagged for vault-hygiene dedupe against two sibling 7.0.1 literature notes created concurrently, above - [[3. Resources/Permanent Notes/Sanitizer Changes Carry Site-Wide Blast Radius]] — a shared sanitizer function's blast radius is every caller, not just the one that triggered the fix - [[3. Resources/Literature Notes/Client-Side Media Processing in WordPress 7.1]] — gap-filled literature note; Permanent already exists (Client-Side Processing Does Not Move the Server Trust Boundary, 2026-07-22) - [[3. Resources/Literature Notes/And Now My Watch Has Ended (Michael Beckwith, WebDevStudios)]] — maintainer/organization separation as a maintenance-continuity risk (CPT UI, WP Search with Algolia) - [[3. Resources/Permanent Notes/Plugin Maintenance Attaches to a Person Not the Organization]] — the maintenance relationship that matters is with the person doing the work, not their employer - [[3. Resources/Literature Notes/Class Action Against Automattic to Proceed After Judge Finds Company Tracked WP Engine Customers]] — sourced here for the single-update-channel security-dependency claim only - [[3. Resources/Permanent Notes/A Single Discretionary Update Channel Is a Security Dependency]] — when one organization's discretion gates the update channel, that discretion is itself a security dependency - [[3. Resources/Literature Notes/GitHub docs to WordPress with DocsPress]] — adjacent to General WordPress-to-WordPress Sync Is Unsolvable - [[3. Resources/Permanent Notes/Unclear Setup Docs Force a Security Decision Onto the User]] — ambiguous setup documentation pushes a security-relevant choice onto the least-informed party - [[3. Resources/Literature Notes/WP Godmode - It's Like Claude Desktop Inside WordPress]] — sponsored product review; an AI agent operating inside wp-admin as a credential/capability surface - [[3. Resources/Permanent Notes/A Site-Modifying Agent Needs Enforced Guardrails Before It Needs More Capability]] — guardrails must be enforced before capability expands, not after - [[3. Resources/Literature Notes/How Can Hosts Communicate Security Risks Without Creating Fear]] — Konik-format literature note for the same Aaron Campbell/Monarx source already linked above from the Readwise/Podcasts folder - [[3. Resources/Permanent Notes/Concrete Steps Convert Alert Anxiety Into Action]] — a security alert paired with a concrete next step reduces anxiety more than the alert alone - [[3. Resources/Literature Notes/WPForms Lite Accused Of Adding Backdoor. I Tested It And Was Surprised]] — independent reproduction of the WPForms Lite backdoor claim; its central claim is already covered by the existing A Privileged Setup Flow Needs Explicit Consent at Every Trust-Boundary Crossing, so no new Permanent - [[3. Resources/Literature Notes/'Blame Nathan subscription service' - This Week in WordPress 383]] — panel digest covering the WordPress 7.0.3 bug-bounty surge among other ecosystem news ## Synthesis additions (2026-08-16, Awesome Motive CDN breach cluster) - [[3. Resources/Literature Notes/Awesome Motive CDN Breach Hits 1.2 Million Sites Running OptinMonster]] — literature note for the CDN-credential-compromise source flagged above (2026-08-11) as a plain external link; ported claim atoms and both permanent candidates from an existing deep-read. - [[3. Resources/Permanent Notes/CDN-Served Plugin JavaScript Bypasses the WordPress Update Trust Boundary]] — a compromised CDN can push malicious plugin JavaScript through the same channel customers trust for legitimate updates. - [[3. Resources/Permanent Notes/A Hijacked Admin Session Executes Attacker Actions Under the Victim's Own Nonce]] — a hijacked admin browser session lets attacker-issued requests carry the victim's own valid nonce. - [[3. Resources/Literature Notes/Awesome Motive Breach Widens]] — a distinct Awesome Motive vulnerability chain from the WPForms Bridge.php backdoor story already in this MOC, confirmed not a duplicate before creating. - [[3. Resources/Permanent Notes/Plugin-Conglomerate Concentration Turns One Flaw Into a Multi-Brand Breach]] — one parent company's shared UpdraftPlus root cause turns a single flaw into a multi-brand breach across its plugin portfolio. - [[3. Resources/Permanent Notes/A Cited CVE and Update Domain Are Both Checkable Before You Act]] — a cited CVE number and update-source domain are independently verifiable before trusting a remediation claim. ## Synthesis additions (2026-08-16, This Week in WordPress #376 roundup) - [[3. Resources/Literature Notes/This Week in WordPress 376]] — multi-topic podcast roundup; its Anthropic-export-ban and CDN-attack permanent candidates duplicated existing notes and were linked rather than recreated. - [[3. Resources/Permanent Notes/An Undefined Legal Category Sweeps In Whatever Technically Fits Its Words]] — undefined terms in "social media" legislation sweep in whatever technically fits the words, regardless of legislative intent. - [[3. Resources/Permanent Notes/A Multi-Year Migrations Technical Rationale Can Expire Before The Migration Does]] — a migration's original technical rationale (CERN/Drupal) can expire before the multi-year migration itself completes. ## Synthesis additions (2026-08-16, performance diagnosis and plugin count) - [[3. Resources/Literature Notes/WordPress Is Slow Usually Means You Stopped Looking Too Early]] — literature note for the source behind the existing A Platform Label Cannot Substitute for a Performance Diagnosis permanent (2026-08-11); only its uncaptured plugin-count claim was promoted separately. - [[3. Resources/Permanent Notes/Plugin Count Is Not a Performance Metric Work Volume Is]] — plugin count alone doesn't measure performance impact; the actual work each plugin does on each request does. ## Synthesis additions (2026-08-16, agency maintenance load) - [[3. Resources/Literature Notes/WordPress Agencies Aren't Afraid of AI. They're Buried in Updates]] — its AI-adoption-inverted-to-pain claim duplicated an existing permanent (2026-08-01) and was linked instead of recreated; only the site-count-vs-headcount claim was new. - [[3. Resources/Permanent Notes/An Agency's Maintenance Load Tracks Site Count Not Headcount]] — an agency's maintenance burden scales with the number of sites it runs, not the size of its team. - [[3. Resources/Literature Notes/Anatomy of a WordPress.org supply-chain attack the six ways in]] — the missing intake record for the provenance/temporal-gap claim already captured verbatim in Point-in-Time Review Cannot Detect an Attack That Unfolds Over Time. - [[3. Resources/Literature Notes/The State of WordPress Agencies in 2026]] — companion sponsored article on the same survey dataset as above; both candidate claims duplicate existing permanents, so no new permanent was created. ## Synthesis additions (2026-08-16, EmDash hosting operations) - [[3. Resources/Literature Notes/One month of EmDash hosting here's what we've sorted]] — literature note for the EmDash hosting operations source already linked above (2026-08-11) as a raw Readwise article; no existing coverage of its dev-endpoint-hardening claim, so a new permanent was created. - [[3. Resources/Permanent Notes/Dev-Only Endpoints Must Be Blocked at the Server Layer in Production]] — a dev-only endpoint left reachable in production is a server-layer configuration failure, not an application bug. ## Synthesis additions (2026-08-16, agent-first WordPress tooling) - [[3. Resources/Literature Notes/An Agent-First Approach to Create Block Theme - Brian Coords]] — literature note ported directly from a full existing deep-read already sitting in the Readwise notes field. - [[3. Resources/Permanent Notes/Agent-First Tooling Exposes Capability Through a CLI Not a New Plugin]] — an agent-first tool exposes its capability through a CLI interface rather than a conventional wp-admin plugin, changing where the security surface sits. - [[3. Resources/Literature Notes/Studio - The Future of AI WordPress Is Now]] — walkthrough of Automattic Studio 2.0 beta's agentic WordPress builder. - [[3. Resources/Permanent Notes/An Agentic Builders Safety Signal Is Convention Adherence Not Output Polish]] — an agentic builder's safety signal is whether its output follows platform convention, not how polished the output looks. ## Synthesis additions (2026-08-17, real-time transport) - [[3. Resources/Literature Notes/Why Real-Time WordPress Is the Future]] — WP Signal's WebSocket relay and core's Real-Time Collaboration polling-transport tradeoff. - [[3. Resources/Permanent Notes/Real-Time Transport Is a Hosting-Layer Gap Not a WordPress-Core Gap]] — the reason WordPress needs third-party WebSocket relays isn't a core capability gap, it's that most WordPress hosts don't support the underlying transport. ## Synthesis additions (2026-08-18, session security and migration trust) - [[3. Resources/Literature Notes/Session Hijacking, Stolen Cookies, and the Blind Spot in WordPress Security Robert Abela]] — session/cookie theft as a distinct, under-addressed WordPress security layer. - [[3. Resources/Permanent Notes/Post-Login Visibility Is a Distinct Security Layer From Authentication Hardening]] — monitoring what happens after a session is established is a separate security layer from hardening the login/authentication step itself. - [[3. Resources/Literature Notes/When the Platform Belongs to Its Users Migrating Daily Kos at Scale Ben Greeley Allison McHenry]] — large-scale WordPress VIP/BuddyPress migration for a major community media site. - [[3. Resources/Permanent Notes/Community Trust Is a Managed Workstream Not a Migration Side Effect]] — preserving community trust through a platform migration requires its own managed workstream, not just technical success. - [[3. Resources/Permanent Notes/Keeping Regulated Data Out of the CMS Database Eases Security Review]] — also homed in Commons & Community Governance MOC (civic-tech angle); routing regulated resident data around the CMS database narrows a security review's scope regardless of which CMS is chosen. ## Synthesis additions (2026-08-21) - [[3. Resources/Literature Notes/Software Supply Chain Security in the Age of AI (Jonathan)]] — two 2026 npm worm-style attacks (Axios, Tanstack) show attackers self-propagating via stolen CI tokens rather than phishing. - [[3. Resources/Literature Notes/Choosing a Trustworthy WordPress Host The Secure Hosting Alliance Trust Seal]] — how agencies/hosts establish verifiable trust instead of relying on marketing claims or affiliate listicles. - [[3. Resources/Literature Notes/Cleaning WordPress Malware Infections With AI]] — responding to an already-infected site with cheap general-purpose AI coding agents instead of $100–$300 commercial scanning services. - [[3. Resources/Literature Notes/WP-CONTENT.CO 285 - Security Release and AI-Agent Credential Debate]] — weekly digest naming the AI-agent-credential-security question (WPVibe/Novamira dispute) as the most durable thread to track. - [[3. Resources/Literature Notes/Surviving the Plugin Stack A Practical Playbook for Auditing Complex WordPress Sites]] — auditing a WordPress site that accumulated dozens of plugins over years without breaking what the business depends on. ## Synthesis additions (2026-08-28 — registering an unhomed note) - [[3. Resources/Permanent Notes/Redundancy Is a Claim About Independence Not a Count of Components]] — registered this run; it was in no MOC. Arrived from a virtual-power-plant source but states a general rule this stack depends on: counting redundant components says nothing about resilience unless you know whether they share a failure cause. The direct application is a hosting stack whose "redundant" layers sit on one provider, one region, or one update channel — see [[3. Resources/Permanent Notes/A Single Discretionary Update Channel Is a Security Dependency]]. ## Synthesis additions (2026-08-28 — cPanel tenant isolation) - [[3. Resources/Literature Notes/Critical cPanel Flaw Could Let One Hosting Customer Take Root Control - Literature Note]] — CVE-2026-65643 crosses the shared-hosting tenant boundary through an ordinary domain-management feature; the source keeps the related Passenger exploitation evidence separate. - [[3. Resources/Permanent Notes/An Advisory Without Detection Guidance Answers Only Half the Question]] — a patch resolves future exposure, while indicators determine whether the operator faces an incident from earlier exploitation. - [[3. Resources/Permanent Notes/Independence Is Decided Per Layer Not Per Stack]] — receives a concrete hosting-control-plane case that WordPress-side hardening cannot reach. ## Synthesis additions (2026-10-05 — backdoor persistence) - [[3. Resources/Readwise/Articles/WordPress Backdoor Rebuilds Itself After Cleanup Using Files, Database, and Shared Memory]] — The Hacker News, summarizing Sucuri's research (Sucuri sells cleanup), reports a backdoor that stores its payload in at least eight places across files, the database and shared memory so each copy can rebuild the others, which makes deleting files alone ineffective. - [[3. Resources/Permanent Notes/Cleaning a Self-Rebuilding Backdoor Means Cutting Execution Before Deleting Files]] — When malware keeps copies in files, the database and shared memory, stop the code that runs first and delete files last, or a surviving copy rebuilds the rest. ## Synthesis additions (2026-10-07 — XSS campaign persistence) - [[3. Resources/Readwise/Articles/Four Ways Back In The WordPress XSS Campaign That Hides Its Own Admin Account]] — Patchstack reports stored-XSS attempts against two plugins (WPC Product Bundles, Ninja Forms) that pull one script and leave four persistence paths, including a hidden administrator and must-use plugins; the vendor sells mitigation rules. - [[3. Resources/Permanent Notes/Patching the Vulnerable Plugin Does Not Evict an Attacker Who Persisted Outside It]] — updating the flawed plugin closes the entry point for the next visitor but leaves persistence in mu-plugins and the database untouched. - [[3. Resources/Permanent Notes/The Users Screen Cannot Prove Who Holds Admin When a Must-Use Plugin Filters It]] — a wp-admin Users screen is output from code an attacker can also run, so who holds administrator rights has to be read from the database. ## Synthesis additions (2026-10-09) - [[3. Resources/Literature Notes/They Should Consider Their WPScan Data — Sybre Waaijer (X, 2026-10-08)]] — reaction to the security funding ask sent to the hosts in this stack; argues researcher treatment belongs in the criteria. ## Synthesis additions (2026-10-18 — registering previously unlisted notes) ### Permanent Notes - [[3. Resources/Permanent Notes/A Deactivated Plugin Still Carries Its CVEs and Autoloaded Bloat]] — Dorman's plugin audit found 20 of 100 plugins deactivated but still on disk, and 62% of one site's autoloaded options belonged to deleted plugins. - [[3. Resources/Permanent Notes/A New Tracking Script Requires a Standing Review Process]] — Adding a tracking pixel or embed is a compliance event that needs manual review in the consent setup, since automated consent scans only back that review up. Closest-fit placement. - [[3. Resources/Permanent Notes/A Security Commons Grows When the Cost of Not Joining Is Visible]] — A cross-competitor security-sharing effort recruits fastest by pointing to a measurable cost each participant already pays alone, not by appealing to collective good. - [[3. Resources/Permanent Notes/A Sync Tool Earns Trust for Destructive Operations by Auto-Backing Up First]] — WordPress Studio's Sync takes an automatic backup before every push or pull, which is what makes overwrite-based deploys safe enough to treat as routine. Closest-fit placement. - [[3. Resources/Permanent Notes/Consent Gating Must Be Verified Not Assumed]] — A consent banner only works if it blocks third-party scripts until opt-in; a banner that displays but doesn't block equals no consent mechanism. Closest-fit placement. - [[3. Resources/Permanent Notes/Local Environments Should Mirror Production Protocol]] — A local environment should match production protocol and URL shape, with HTTPS and real-looking domains, so HTTPS-only bugs show up before deploy. Closest-fit placement. - [[3. Resources/Permanent Notes/Managed Hosting Collapses the Setup Friction That Gates Self-Hosted AI Agents]] — When a managed host builds self-hosted AI agent support into provisioning, setup shrinks from a multi-tool technical task to a guided sequence a non-developer finishes in minutes. Closest-fit placement. - [[3. Resources/Permanent Notes/Openness and Attack Surface Are the Same Property Viewed Two Ways]] — A platform's extensibility and its attack surface are one property seen from two angles, so making it safer almost always means making it less open. - [[3. Resources/Permanent Notes/Revocation Power Is What Separates a Trust Seal From a Badge]] — A self-regulatory trust seal is only as trustworthy as its willingness to revoke certification from a member that stops complying; without that it's a badge. - [[3. Resources/Permanent Notes/The QUERY HTTP Method Moves PII Out of Access Logs]] — The QUERY HTTP method, RFC 10008, lets a safe read carry a body instead of a querystring, keeping sensitive parameters out of plaintext access logs. Closest-fit placement. - [[3. Resources/Permanent Notes/WordPress Maintenance Mode Does Not Isolate a Compromised Site]] — WordPress maintenance mode doesn't block direct access to backdoor files, so isolating a compromised site means cutting network access, such as DNS-forwarding to a static page. - [[3. Resources/Permanent Notes/Zet · Plugin allowlists reduce production incidents]] — Plugin allowlists reduce production incidents for enterprises that have CI and code review, with security incident logs as the check. ### Literature Notes - [[3. Resources/Literature Notes/'Fake Cat on a Fishing Rod' - This Week in WordPress 381]] — A panel reports a pre-auth WordPress RCE found for about $25 of AI compute and patched in 7.0.2, with a 24-hour private head start for hosts and CDNs. - [[3. Resources/Literature Notes/3 Things All Website Owners Need to Check for Privacy Compliance Hans Skillrud]] — Hans Skillrud's talk lists three privacy compliance checks for website owners, including testing whether consent tools really block third-party scripts before opt-in. Closest-fit placement. - [[3. Resources/Literature Notes/Developer Traces 13-Year Backdoor Campaign Across 44 WordPress.org Plugins]] — A developer traced a 13-year backdoor campaign across 44 WordPress.org plugins, using burner accounts and non-PHP payloads hidden in plugin files. - [[3. Resources/Literature Notes/Is Your Multicloud Pipeline Compliant Devops vs GitOps]] — For regulated multicloud markets, GitOps makes drift mechanically detectable and turns commit history into the audit trail compliance frameworks demand. Closest-fit placement. - [[3. Resources/Literature Notes/Syed Balkhi (Awesome Motive) put a backdoor in WPForms Lite]] — A thread reports WPForms Lite v2.0.0 silently hands a WPForms-hosted app a one-hour admin login token during setup, which the author calls a backdoor by definition. - [[3. Resources/Literature Notes/The Query Method - A new HTTP verb]] — RFC 10008, published June 2026, defines the HTTP QUERY method, combining GET's safe reads with a request body so sensitive data stays out of URLs and server logs. Closest-fit placement. - [[3. Resources/Literature Notes/WP Tavern podcast 224 David Snead on Secure Hosting Alliance]] — David Snead describes the Internet Infrastructure Forum's shared abuse-data model for hosts and registrars, driven by business self-interest, not moral appeal. - [[3. Resources/Literature Notes/Why WordPress Security Holds Up Against the Competition]] — Vlad of Scala Hosting argues WordPress security rests on good practice and AI integration, and that revenue sites should leave shared hosting, a pitch matching the employer's products.