WordPress / WordPress/WordPress-Coding-Standards

Don't require sanitization with wp_verify_nonce()

Open
#869 32 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Focus: Security Status: Awaiting feedback
Dominant language
PHP
Stars
2.8k
Forks
521
Avg merge
5d 20h
Merged PRs (30d)
1

Description

Don't require sanitization (wp_unslash, sanitize_text_field) with wp_verify_nonce().

cc @mjangda

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the PHP_CodeSniffer sniff that requires wp_unslash or sanitize_text_field before wp_verify_nonce(), then review its existing tests and the issue discussion for the intended exception. Done means the rule no longer requires those sanitization calls for wp_verify_nonce() while existing related checks still pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.