Skip to content

Security/EscapeOutput: make basename( __FILE__ ) pattern matching case-insensitive#2729

Open
rodrigoprimo wants to merge 1 commit intodevelopfrom
fix-escape-output-basename-case-insensitive
Open

Security/EscapeOutput: make basename( __FILE__ ) pattern matching case-insensitive#2729
rodrigoprimo wants to merge 1 commit intodevelopfrom
fix-escape-output-basename-case-insensitive

Conversation

@rodrigoprimo
Copy link
Copy Markdown
Collaborator

Description

The WordPress.Security.EscapeOutputsniff has special handling for _deprecated_file() calls where the first parameter follows the basename( __FILE__ ) pattern.

The regex pattern was case-sensitive, which meant it would only match lowercase basename() and uppercase __FILE__. This is incorrect because both function names and magic constants (https://3v4l.org/8nAEV and https://www.php.net/manual/en/language.constants.magic.php) in PHP are case-insensitive.

This PR fixes the regex pattern to be case-insensitive.

Suggested changelog entry

WordPress.Security.EscapeOutput: false negative for _deprecated_file() calls when the basename( __FILE__ ) pattern used non-standard casing for basename() and/or __FILE__.

…e-insensitive

The sniff has special handling for `_deprecated_file()` calls where the first parameter follows the `basename( __FILE__ )` pattern.

The regex pattern was case-sensitive, which meant it would only match lowercase `basename()` and uppercase `__FILE__`. This is incorrect because both function names and magic constants (https://3v4l.org/8nAEV and https://www.php.net/manual/en/language.constants.magic.php) in PHP are case-insensitive.

This commit fixes the regex pattern to be case-insensitive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant