Skip to content

Bash WP-CLI Update v8.1.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 16:15
· 10 commits to main since this release

Security release for CVE-2026-119977, with the licence changed to MIT. The repository
documentation work staged under [Unreleased] before this release ships in the same
commit and is listed here rather than hidden in the git log.

Added

  • --security (read-only): reads each site's WordPress core version, compares it
    with the fixed releases for CVE-2026-119977 and prints a per-site verdict. Exit 1
    means at least one site is exposed (or its version cannot be read); exit 0 means
    every site is at or above the fixed release for its branch. It takes no lock and no
    backup, so monitoring can call it every minute.
  • --harden: appends a marker-guarded block to each site's root .htaccess
    denying web access to wp-content/upgrade/
    (RewriteRule ^wp-content/upgrade/ - [F,L]), for Apache and LiteSpeed. The block is
    idempotent and an existing .htaccess is copied once to
    .htaccess.wp-cli-update.bak before the first change. The nginx directive
    (location ^~ /wp-content/upgrade/ { deny all; }) is printed at the end of the run,
    because nginx ignores .htaccess.
  • --harden-upgrade-dir / --no-harden-upgrade-dir and the HARDEN_UPGRADE_DIR
    configuration key: apply the same block as part of every writing mode (default 0).
    --security, --health and --check refuse the flag with exit 2, because they are
    read-only.
  • A CVE column in --health (safe, UPDATE or ?) and the cve_2026_119977
    field in its JSON Lines record.
  • The GitHub wiki as versioned sources. wiki/ holds the pages and the manifest;
    ghagent wiki build|verify|publish renders the sidebar and footer and pushes the
    built tree to the wiki repository, so a page cannot be published with a broken link.
  • Community files: CODE_OF_CONDUCT.md, SUPPORT.md, CITATION.cff,
    .github/ISSUE_TEMPLATE/ (bug and feature forms plus contact links),
    .github/PULL_REQUEST_TEMPLATE.md, .github/CODEOWNERS and
    .github/dependabot.yml.
  • A rendered banner and social preview (assets/social-preview.png and .svg),
    and a .ghagent.json that records how the repository is checked.
  • docs/AGENT-INSTALL.md, docs/AGENT-OPERATIONS.md and docs/DEVELOPMENT.md:
    the install, operations and development material that used to live in AGENTS.md.

Changed

  • The licence is MIT. LICENSE, package.json, CITATION.cff, the README badge
    and the wiki now say MIT; commercial use no longer needs a separate agreement. The
    legacy/ archive keeps the licence text it was published under.
  • A --core/--full run reports a site that stays below the fixed release instead
    of assuming the update did its job: the log names the CVE and the release to reach.
  • AGENTS.md is now a map. It keeps the two overriding rules, the file table, the
    verification order in brief and the absolute do-nots, and links to the detailed
    documents — the length a reader, and an agent, can afford on every request.
  • README.md gained the current version in the title, a badge row, the social
    preview, a navigation row, a table of contents, the security section and a "For
    agents" pointer; every code fence now carries a language tag.
  • CHANGELOG.md uses ## [x.y.z] - YYYY-MM-DD headings throughout (the finder
    version moved into this preamble), has an [Unreleased] section and canonical change
    types; the release-lineage table moved to docs/RELEASE-HISTORY.md.
  • docs/README.md indexes the new documents; CONTRIBUTING.md points at
    docs/DEVELOPMENT.md for the extension procedure.
  • The npm author field no longer carries a personal e-mail address; the repository
    profile is the contact route.
  • The published wiki is now generated from wiki/; the placeholder Home page is
    replaced by the manual, including the CVE-2026-119977 runbook.

Fixed

  • The README title said 8.0.0 while the tree shipped 8.0.4, and PROJECT_MAP.md
    had a truncated table row — a dependency list cut in the middle of a word.
  • README.md §7 and SECURITY.md still described the pre-8.0.3 backup layout
    (1777 with the sticky bit). The code has created the tree 0700 and moved the dump
    in as root:root 0640 since 8.0.3; both documents now say so, and REFACTORING.md
    marks its 6.2.0 entry as superseded.
  • The privacy check found a fake GitHub token literal in tests/test_secretguard.sh
    and a third-party e-mail address quoted in ANALYSIS.md and in this file. The test
    value is now assembled at run time; the address is described, not repeated.
  • tests/test_secretguard.sh used an unroutable example.invalid git identity; it is
    now example.com, the reserved documentation domain, which needs no exception.
  • The temporary secret-scan allowlist entry for CITATION.cff is gone with the licence
    change: license: MIT is below the scanner's minimum value length.

Security

  • WordPress CVE-2026-119977 (race condition in the core updater; CVSS 8.1; CISA KEV
    since 2026-11-03): affected core 4.7 through 7.1.3; fixed releases 7.1.4, 7.0.8 on
    the 7.0 branch, 6.9.11 on the 6.9 branch and 4.7.39 on the 4.7 branch; 4.6 and older
    have no fix. The tool now detects exposed sites (--security, the --health CVE
    column) and can close the upgrade directory on Apache and LiteSpeed (--harden,
    HARDEN_UPGRADE_DIR), printing the nginx directive that nginx needs instead.