# WordPress 7.0.1 Now Available, Fixes 31 Bugs > [!question] Lingering Questions > - Was one week of RC testing (RC1 July 1 → final) enough given how broad 7.0's admin/block changes were, or should point releases after milestone releases get longer bake time? > - Will the `wp_kses()` regression prompt tighter regression tests specifically around sanitization of inline styles going forward? > [!tip] Article Ideas > - A short "sanitizer changes carry site-wide blast radius" piece using the `wp_kses()` regression as the worked example — pairs with the parser-differential security note already in the vault. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/A Parser Disagreement Between Two Sanitizers Is the Exploitable Seam]] — different failure mode (two sanitizers disagreeing) but the same underlying lesson: shared sanitization functions have outsized blast radius. > [!quote] Vocabulary > - *maintenance release* — a point release (7.0 → 7.0.1) that fixes bugs/regressions without adding features. > - `wp_kses()` — WordPress's core HTML-sanitization function; the regression here stripped valid `background-image: url(…)` CSS down to a bare `style=")"`. ## Metadata - Source: [[3. Resources/Readwise/Articles/WordPress 7.0.1 Now Available, Fixes 31 Bugs]] - URL: https://www.therepository.email/wordpress-7-0-1-now-available-fixes-31-bugs ## Author's thesis WordPress 7.0.1 is a routine but consequential maintenance release: 31 bug fixes, 14 of them in the block editor, concentrated in the exact areas 7.0 "Armstrong" changed most (block editor, admin reskin, media) — with the standout fix resolving a `wp_kses()` sanitizer regression that had been corrupting valid inline CSS background images site-wide. ## Key arguments (≤3) 1. **Milestone releases predictably generate a regression surface**, and a fast maintenance follow-up is the mitigation pattern — the 31 fixes cluster almost entirely in what 7.0 touched (block editor, reskin, media), not scattered across the codebase. 2. **The `wp_kses()` regression is the headline developer-facing fix**: a single change to a shared sanitization function broke every theme/plugin relying on inline `background-image` CSS, stripping the declaration to `style=")"`. 3. **Release cadence context matters**: RC1 landed July 1, giving roughly a week of testing before final — a genuinely fast turnaround for a release fixing this much surface area. ## Claim atoms ### wp_kses regression corrupted inline background-image CSS > [!quote] ID:rw_manual > a regression in `wp_kses()` — the function WordPress uses to sanitize HTML — that was corrupting valid CSS `background-image: url(…)` declarations, stripping them down to a bare `style=")"` Where/why: the headline developer-facing fix in 7.0.1; matters because sanitization changes have site-wide blast radius — one regression hit every theme/plugin using inline background images. ### Maintenance releases stabilize milestone-release regression surface > [!quote] ID:rw_manual > addresses issues in the block editor, admin UI, and media, all areas that saw significant changes in 7.0's milestone update Where/why: explains why the 31 fixes cluster where they do — a release-management pattern worth naming: big feature releases predictably need a fast follow-up. ## Permanent candidates - **Sanitizer changes carry site-wide blast radius** — a change to a shared sanitization function like `wp_kses()` can break every consumer of a given markup pattern at once. Strong candidate: general principle, reusable well beyond this one release. → promoted below. ## Processing checklist - [x] Pull claim atoms and permanent candidates from the existing deep-read notes - [x] Connect into the relevant MOC — [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] - [ ] Watch WordPress 7.1 (Aug 19, WordCamp US) for whether inline-style sanitization gets explicit regression tests ## Links - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — a shared-sanitizer regression is a security/reliability-adjacent core-maintenance failure mode relevant to the hosting-security stack thread.