fix(security): eliminate false positives in NonceVerification for empty/isset#1355
Open
faisalahammad wants to merge 7 commits into
Open
Conversation
…ty/isset - Add custom PluginCheck.Security.NonceVerificationSniff extending WPCS sniff - Override needs_nonce_check() to return false for empty()/isset() contexts - These only check existence, not process form data - Update rulesets to use custom sniff instead of WPCS one - Add unit tests for false positive cases (empty/isset) and true positives Fixes WordPress#1350
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov bricked their old Keybase account causing GPG signature verification to fail. Updated pinned SHA from v6.0.1 to v6.0.2 which uses the new keybase URL. Refs WordPress#1350
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
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.
Summary
The WPCS
NonceVerificationSniffincorrectly flagsempty()andisset()checks on superglobals as "Processing form data without nonce verification". These functions only check existence, they don't process form data values.Created a custom
PluginCheck.Security.NonceVerificationsniff that extends the WPCS sniff and overridesneeds_nonce_check()to returnfalseforempty()/isset()contexts.Fixes #1350
Changes
phpcs-sniffs/PluginCheck/Sniffs/Security/NonceVerificationSniff.php (new)
Custom sniff extending WPCS
NonceVerificationSniff. Overridesneeds_nonce_check()to treatempty()/isset()as safe.phpcs-rulesets/plugin-check.ruleset.xml
Switched from
WordPress.Security.NonceVerificationtoPluginCheck.Security.NonceVerification.Before:
After:
phpcs-sniffs/PluginCheck/ruleset.xml
Registered the new custom sniff.
After:
Testing
Test 1: False positive - empty() on superglobal
Result: No warning (fixed)
Test 2: False positive - wrapper function with empty() check
Result: No false positive on empty() check
Test 3: True positive - direct superglobal processing
Result: Error "Processing form data without nonce verification" (still caught)
All 14 PHPCS sniff tests pass,
composer lintpasses,composer phpstanpasses, CodeRabbit review clean.