Security-only short-cycle release: RCE in the WordPress upgrade process (upgrade window); stored XSS
in crafted block markup, privacy data-removal requests, the Interactivity API, customizer selective
refresh, the Categories block, crafted user logins, playlists/image blocks, and the core/comments-pagination-next|previous blocks; stored DoS in the Interactivity API; unauth
discovery of unpublished customizer changesets; a note-read authorization weakness for privileged
users; bundled root-cert CA refresh (eMudhra revocation).
Operator Action Required
No breaking changes — no migration, no new/renamed config. Tag-only bump.
Advisories: deterministic scan found 0 CVEs classifiable for this window (its 27 unclassified
entries are all MariaDB/server, not in this window); the security value is the 7.1.4 release notes
above. No CVE ids are published in those notes yet.
Open PR #2 (pr-20261021-190326, PHP/session hardening on 7.1.3) is left untouched. 7.1.4 is a
fresh current-PHP build; if both merge this PR's tag wins, and #2 may then be redundant.
atmoz/sftp:alpine is left as-is: Docker Hub has no newer versioned tag (only floating alpine/debian variants), so there is nothing pin-able to bump.
Recommended release command (run after merge; this PR does not touch the version label)
abra recipe release wordpress -z
Live verification (pre-PR, direct deploy on cc-ci)
Deployed the WIP branch directly with abra app deploy --chaos on the local swarm
(dev-wordpress, torn down afterwards): app converged to wordpress:7.1.4 + mariadb:13.0, wp core version = 7.1.4, wp core verify-checksums PASS, installer + REST index OK, /wp-json/wp/v2/settings 401 unauth, /xmlrpc.php 405 on GET, post create/read OK, and an
authenticated XML-RPC wp.getUsersBlogs round-trip succeeded.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
## WordPress 7.1.3 → 7.1.4 (security release)
| service | current | new |
|---------|---------|-----|
| app | `wordpress:7.1.3` | `wordpress:7.1.4` |
| db | `mariadb:13.0` | no change (13.0 is latest stable; 13.1.x are `-rc`) |
| ftp (optional overlay) | `atmoz/sftp:alpine` | no change (no versioned upstream tag) |
**Upstream release notes:** wordpress 7.1.3→7.1.4: https://wordpress.org/news/2026/10/wordpress-7-1-4/
**Image tags:** https://hub.docker.com/_/wordpress (7.1.4 published 2026-10-29)
### What 7.1.4 fixes
Security-only short-cycle release: RCE in the WordPress upgrade process (upgrade window); stored XSS
in crafted block markup, privacy data-removal requests, the Interactivity API, customizer selective
refresh, the Categories block, crafted user logins, playlists/image blocks, and the
`core/comments-pagination-next|previous` blocks; stored DoS in the Interactivity API; unauth
discovery of unpublished customizer changesets; a note-read authorization weakness for privileged
users; bundled root-cert CA refresh (eMudhra revocation).
### Operator Action Required
- **No breaking changes** — no migration, no new/renamed config. Tag-only bump.
- Advisories: deterministic scan found 0 CVEs classifiable for this window (its 27 unclassified
entries are all MariaDB/server, not in this window); the security value is the 7.1.4 release notes
above. No CVE ids are published in those notes yet.
- Open PR #2 (`pr-20261021-190326`, PHP/session hardening on 7.1.3) is left untouched. 7.1.4 is a
fresh current-PHP build; if both merge this PR's tag wins, and #2 may then be redundant.
- `atmoz/sftp:alpine` is left as-is: Docker Hub has no newer versioned tag (only floating
`alpine`/`debian` variants), so there is nothing pin-able to bump.
### Recommended release command (run after merge; this PR does not touch the version label)
abra recipe release wordpress -z
### Live verification (pre-PR, direct deploy on cc-ci)
Deployed the WIP branch directly with `abra app deploy --chaos` on the local swarm
(`dev-wordpress`, torn down afterwards): app converged to `wordpress:7.1.4` + `mariadb:13.0`,
`wp core version` = 7.1.4, `wp core verify-checksums` PASS, installer + REST index OK,
`/wp-json/wp/v2/settings` 401 unauth, `/xmlrpc.php` 405 on GET, post create/read OK, and an
authenticated XML-RPC `wp.getUsersBlogs` round-trip succeeded.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
WordPress 7.1.3 → 7.1.4 (security release)
wordpress:7.1.3wordpress:7.1.4mariadb:13.0-rc)atmoz/sftp:alpineUpstream release notes: wordpress 7.1.3→7.1.4: https://wordpress.org/news/2026/10/wordpress-7-1-4/
Image tags: https://hub.docker.com/_/wordpress (7.1.4 published 2026-10-29)
What 7.1.4 fixes
Security-only short-cycle release: RCE in the WordPress upgrade process (upgrade window); stored XSS
in crafted block markup, privacy data-removal requests, the Interactivity API, customizer selective
refresh, the Categories block, crafted user logins, playlists/image blocks, and the
core/comments-pagination-next|previousblocks; stored DoS in the Interactivity API; unauthdiscovery of unpublished customizer changesets; a note-read authorization weakness for privileged
users; bundled root-cert CA refresh (eMudhra revocation).
Operator Action Required
entries are all MariaDB/server, not in this window); the security value is the 7.1.4 release notes
above. No CVE ids are published in those notes yet.
pr-20261021-190326, PHP/session hardening on 7.1.3) is left untouched. 7.1.4 is afresh current-PHP build; if both merge this PR's tag wins, and #2 may then be redundant.
atmoz/sftp:alpineis left as-is: Docker Hub has no newer versioned tag (only floatingalpine/debianvariants), so there is nothing pin-able to bump.Recommended release command (run after merge; this PR does not touch the version label)
abra recipe release wordpress -z
Live verification (pre-PR, direct deploy on cc-ci)
Deployed the WIP branch directly with
abra app deploy --chaoson the local swarm(
dev-wordpress, torn down afterwards): app converged towordpress:7.1.4+mariadb:13.0,wp core version= 7.1.4,wp core verify-checksumsPASS, installer + REST index OK,/wp-json/wp/v2/settings401 unauth,/xmlrpc.php405 on GET, post create/read OK, and anauthenticated XML-RPC
wp.getUsersBlogsround-trip succeeded.Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
wordpress@cea471c8✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.