Skip to content

fix(VUL-25719): bump wp-coding-standards/wpcs from 3.3.0 to 3.4.1 - #492

Merged
pwtyler merged 2 commits into
mainfrom
vuln-VUL-25719
Aug 4, 2026
Merged

pwtyler merged 2 commits into
mainfrom
vuln-VUL-25719

Conversation

@service-samwise

@service-samwise service-samwise commented Jul 29, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Bumps wp-coding-standards/wpcs from 3.3.0 to 3.4.1 to resolve CVE-2026-45293 (arbitrary code execution in WordPress Coding Standards). Also updates two transitive dependencies that wpcs 3.4.1 requires at higher minimum versions.

Addresses: VUL-25719

CVEs

Package CVE Severity Description Fixed In
wp-coding-standards/wpcs CVE-2026-45293 High Arbitrary code execution vulnerability in WordPress Coding Standards (WordPressCS) 3.4.1

Changes

  • composer.lock only — wp-coding-standards/wpcs is a transitive dependency (pulled in by pantheon-systems/pantheon-wp-coding-standards and automattic/vipwpcs). It is not listed in composer.json, so only the lockfile is updated.
  • wp-coding-standards/wpcs: 3.3.0 → 3.4.1
  • phpcsstandards/phpcsextra: 1.5.0 → 1.5.1 (required by wpcs 3.4.1: ^1.5.1)
  • phpcsstandards/phpcsutils: 1.2.2 → 1.2.3 (required by wpcs 3.4.1: ^1.2.3 and phpcsextra 1.5.1: ^1.2.3)

Risk assessment

Low — lockfile-only patch/minor bump into a dev-only coding standards tool (used exclusively by the lint CI job). wp-coding-standards/wpcs is a phpcodesniffer-standard type package; it is not imported at runtime by the plugin itself and cannot affect plugin behavior in production.

Layer Score Evidence
Pre-merge detection strong 7 PHP test files, behat and phpunit suites; lint + behat jobs run on PRs
Deployment safety unknown deploy config lives in WordPress.org pipeline; no staging layer visible in repo
Production detection unknown WordPress plugin — observability config not in repo
Recovery speed partial release-please present; 3 releases in last ~14 months

Bump: wp-coding-standards/wpcs 3.3.0 → 3.4.1 (minor); transitive deps patch.

Addresses CVE fixed in wp-coding-standards/wpcs v3.4.1:
- CVE-2026-45293: Arbitrary code execution vulnerability in WordPress Coding Standards (WordPressCS)

Also bumps transitive dependencies required by wpcs 3.4.1:
- phpcsstandards/phpcsextra 1.5.0 -> 1.5.1
- phpcsstandards/phpcsutils 1.2.2 -> 1.2.3
@service-samwise
service-samwise requested a review from a team as a code owner July 29, 2026 01:50
@github-actions

Copy link
Copy Markdown
Contributor
Composer Changes
Dev Packages Operation Base Target
phpcsstandards/phpcsextra Upgraded 1.5.0 1.5.1
phpcsstandards/phpcsutils Upgraded 1.2.2 1.2.3
wp-coding-standards/wpcs Upgraded 3.3.0 3.4.1

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@tundeafolabi tundeafolabi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@pwtyler
pwtyler merged commit 74b9ce4 into main Aug 4, 2026
23 of 24 checks passed
@pwtyler
pwtyler deleted the vuln-VUL-25719 branch August 4, 2026 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants