Prepare CHANGELOG for the PHP 7.0.1 security release - #283
Merged
Conversation
Documents the wp-coding-standards/wpcs 3.4.0 -> 3.4.1 bump (PR #282) as a security release. Both Required and Required-Strict include WordPress-Extra, so both were exposed to the arbitrary command execution in the WordPress.WP.EnqueuedResourceParameters sniff (CVE-2026-45293). Also notes that 7.0.0 is now uninstallable rather than merely vulnerable: it pins the affected wpcs 3.4.0 exactly, and Composer 2.10+ refuses to resolve advisory-affected versions by default. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Updates the requirements on [wp-coding-standards/wpcs](https://github.com/WordPress/WordPress-Coding-Standards) to permit the latest version. - [Release notes](https://github.com/WordPress/WordPress-Coding-Standards/releases) - [Changelog](https://github.com/WordPress/WordPress-Coding-Standards/blob/develop/CHANGELOG.md) - [Commits](WordPress/WordPress-Coding-Standards@3.4.0...3.4.1) --- updated-dependencies: - dependency-name: wp-coding-standards/wpcs dependency-version: 3.4.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Documents the wp-coding-standards/wpcs 3.4.0 -> 3.4.1 bump (PR #282) as a security release. Both Required and Required-Strict include WordPress-Extra, so both were exposed to the arbitrary command execution in the WordPress.WP.EnqueuedResourceParameters sniff (CVE-2026-45293). Also notes that 7.0.0 is now uninstallable rather than merely vulnerable: it pins the affected wpcs 3.4.0 exactly, and Composer 2.10+ refuses to resolve advisory-affected versions by default. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…-standards into changelog-php-7.0.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the
wp-coding-standards/wpcs3.4.0 → 3.4.1 bump as a security release. Depends on #282 — merge that first, then this, then push the signed7.0.1tag.Why this is a security release
CVE-2026-45293 (CWE-95, CVSS 8.6 high):
WordPress.WP.EnqueuedResourceParametersreconstructed function arguments and ran them througheval()inis_falsy(). Scanning untrusted PHP — a CI job linting a pull request, or reviewing third-party code locally — could execute arbitrary commands on the scanning host.We were exposed in both standards.
Required/ruleset.xmlincludesWordPress-Extra, andRequired-StrictinheritsRequired. Verified with a benign PoC in a throwaway worktree:eval(in sniffThe part that raises urgency
Composer 2.10's
policy.advisories.blockdefaults to on, socomposer updateagainst currentmasterfails to resolve at all:Because 7.0.0 pins the affected 3.4.0 exactly, the released package is uninstallable for consumers on Composer 2.10+, not merely vulnerable. Shipping 7.0.1 is what unblocks
composer update.Verification
With #282 applied: dependencies resolve cleanly (pulling PHPCSUtils 1.2.3, PHPCSExtra 1.5.1) and
composer testpasses all four smoke assertions acrossRequiredandRequired-Strict.Follow-up
The exact-pin policy is worth a separate discussion — an upstream patch now requires a coordinated release here, and blocks consumers until it lands. Filed separately; no constraint change in this PR.
🤖 Generated with Claude Code