(Re-run 2026-10-09: PR #1 previously carried 7.1.0; extended onto current upstream main bfe9a099 = recipe 4.1.0+7.1.2 and bumped the app to 7.1.3.)
service | image | current | new
app | wordpress | 7.1.2 | 7.1.3
db | mariadb | 13.0 | 13.0 (unchanged — abra: already the latest)
ftp (optional overlay)| atmoz/sftp | alpine | alpine (unchanged — floating tag, abra-unparseable)
The coop-cloud.${STACK_NAME}.version label is intentionally untouched (stays 4.1.0+7.1.2) — it is bumped by the release step below, not in this PR.
Operator Action Required
WordPress 7.1.3 (2026-10-06) is a maintenance & security release — 7 security fixes + 4 bug fixes; the announcement recommends updating immediately. The 7 security issues:
Stored XSS on the Comments administration page, exploitable via pending comments (Trail of Bits + OpenAI)
DoS in WP_Http::make_absolute_url() (Anthropic)
Second-order SQL injection in the WordPress WXR export (Anthropic)
A weakness allowing Author-role users to sticky posts (Anthropic)
Unauthenticated disclosure of comments on private & unpublished posts — CVE-2026-66666 (CVSS 6.9, Patchstack)
Imgur embeds vulnerable to XSS
Forgeable parameters passed to the {status}_{type} hook can lead to action-name collision
No compose/config/env/volume changes and no DB schema migration required — image-tag bump only. PHP requirement is unchanged (the official image ships PHP 8.3.x). Site-/plugin-level review only if you rely on the affected admin/embed paths.
Recommended release command (operator, after the upstream PR merges):
abra recipe release wordpress -z
(patch bump — security + maintenance release, no recipe-level breaking changes; the release step syncs the version label to a.b.c+7.1.3 and tags)
Verification (direct dev deploy on cc-ci, 2026-10-09, torn down after)
abra app deploy --chaos on the local swarm (dev-wordpress.ci.commoninternet.net) from this branch head f53b93a: converged — app wordpress:7.1.3 1/1 (Apache/2.4.68, PHP/8.3.35), db mariadb:13.0 1/1 (13.0.2).
Confirmed the running version inside the container: wp core version → 7.1.3 (wp-includes/version.phpwp_version = '7.1.3'); core copied cleanly, wp-content volume + recipe-templated .htaccess preserved; healthcheck GET / → 302 (fresh-install wizard, expected — the CI env runs no core_install).
## wordpress upgrade: 7.1.2 → 7.1.3
_(Re-run 2026-10-09: PR #1 previously carried 7.1.0; extended onto current upstream main `bfe9a099` = recipe 4.1.0+7.1.2 and bumped the app to 7.1.3.)_
```
service | image | current | new
app | wordpress | 7.1.2 | 7.1.3
db | mariadb | 13.0 | 13.0 (unchanged — abra: already the latest)
ftp (optional overlay)| atmoz/sftp | alpine | alpine (unchanged — floating tag, abra-unparseable)
```
The `coop-cloud.${STACK_NAME}.version` label is intentionally untouched (stays `4.1.0+7.1.2`) — it is bumped by the release step below, not in this PR.
### Operator Action Required
WordPress **7.1.3** (2026-10-06) is a **maintenance & security release** — 7 security fixes + 4 bug fixes; the announcement recommends updating immediately. The 7 security issues:
- Stored XSS on the Comments administration page, exploitable via pending comments (Trail of Bits + OpenAI)
- DoS in `WP_Http::make_absolute_url()` (Anthropic)
- Second-order SQL injection in the WordPress WXR export (Anthropic)
- A weakness allowing Author-role users to sticky posts (Anthropic)
- Unauthenticated disclosure of comments on private & unpublished posts — **CVE-2026-66666** (CVSS 6.9, Patchstack)
- Imgur embeds vulnerable to XSS
- Forgeable parameters passed to the `{status}_{type}` hook can lead to action-name collision
No compose/config/env/volume changes and no DB schema migration required — image-tag bump only. PHP requirement is unchanged (the official image ships PHP 8.3.x). Site-/plugin-level review only if you rely on the affected admin/embed paths.
**Upstream release notes:** app wordpress 7.1.2→7.1.3: https://wordpress.org/news/2026/10/wordpress-7-1-3-maintenance-and-security-release/ (db and ftp unchanged)
Recommended release command (operator, after the upstream PR merges):
`abra recipe release wordpress -z`
(patch bump — security + maintenance release, no recipe-level breaking changes; the release step syncs the version label to `a.b.c+7.1.3` and tags)
### Verification (direct dev deploy on cc-ci, 2026-10-09, torn down after)
- `abra app deploy --chaos` on the local swarm (`dev-wordpress.ci.commoninternet.net`) from this branch head `f53b93a`: converged — app **`wordpress:7.1.3` 1/1** (Apache/2.4.68, PHP/8.3.35), db `mariadb:13.0` 1/1 (13.0.2).
- Confirmed the running version inside the container: `wp core version` → **7.1.3** (`wp-includes/version.php` `wp_version = '7.1.3'`); core copied cleanly, `wp-content` volume + recipe-templated `.htaccess` preserved; healthcheck `GET /` → 302 (fresh-install wizard, expected — the CI env runs no `core_install`).
- Dev deploy removed afterwards (0 stacks / 0 volumes / 0 secrets leaked).
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 upgrade: 7.1.2 → 7.1.3
(Re-run 2026-10-09: PR #1 previously carried 7.1.0; extended onto current upstream main
bfe9a099= recipe 4.1.0+7.1.2 and bumped the app to 7.1.3.)The
coop-cloud.${STACK_NAME}.versionlabel is intentionally untouched (stays4.1.0+7.1.2) — it is bumped by the release step below, not in this PR.Operator Action Required
WordPress 7.1.3 (2026-10-06) is a maintenance & security release — 7 security fixes + 4 bug fixes; the announcement recommends updating immediately. The 7 security issues:
WP_Http::make_absolute_url()(Anthropic){status}_{type}hook can lead to action-name collisionNo compose/config/env/volume changes and no DB schema migration required — image-tag bump only. PHP requirement is unchanged (the official image ships PHP 8.3.x). Site-/plugin-level review only if you rely on the affected admin/embed paths.
Upstream release notes: app wordpress 7.1.2→7.1.3: https://wordpress.org/news/2026/10/wordpress-7-1-3-maintenance-and-security-release/ (db and ftp unchanged)
Recommended release command (operator, after the upstream PR merges):
abra recipe release wordpress -z(patch bump — security + maintenance release, no recipe-level breaking changes; the release step syncs the version label to
a.b.c+7.1.3and tags)Verification (direct dev deploy on cc-ci, 2026-10-09, torn down after)
abra app deploy --chaoson the local swarm (dev-wordpress.ci.commoninternet.net) from this branch headf53b93a: converged — appwordpress:7.1.31/1 (Apache/2.4.68, PHP/8.3.35), dbmariadb:13.01/1 (13.0.2).wp core version→ 7.1.3 (wp-includes/version.phpwp_version = '7.1.3'); core copied cleanly,wp-contentvolume + recipe-templated.htaccesspreserved; healthcheckGET /→ 302 (fresh-install wizard, expected — the CI env runs nocore_install).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@e3602260✅ passed → https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/1301(summary card unavailable — see the run for details.) full logs · dashboard
!testme
🌻 cc-ci —
wordpress@5e46fa3f✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
wordpress@c6e598d5✅ passedfull logs · dashboard
chore: upgrade wordpress to 7.1.0to chore: upgrade wordpress to 7.1.3!testme
🌻 cc-ci —
wordpress@a40f5458✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.