Skip to content

Ajax: Sanitize dashboard widget AJAX request parameters. - #12375

Open
manishdhorepatil-art wants to merge 1 commit into
WordPress:trunkfrom
manishdhorepatil-art:Ticket-11661
Open

manishdhorepatil-art wants to merge 1 commit into
WordPress:trunkfrom
manishdhorepatil-art:Ticket-11661

Conversation

@manishdhorepatil-art

Copy link
Copy Markdown

Summary

This PR sanitizes the pagenow and widget request parameters in
wp_ajax_dashboard_widgets().

Change log:

  • Add Sanitize $_GET['pagenow'] using sanitize_key( wp_unslash() ).
  • Sanitize $_GET['widget'] using sanitize_key( wp_unslash() ).
  • Replace direct use of $_GET['widget'] with the sanitized local variable.

Testing

  • Applied the patch.
  • Verified Dashboard widgets continue to load correctly.
  • Tested valid and invalid values for pagenow and widget.
  • Confirmed no regressions were observed.

Trac ticket: https://core.trac.wordpress.org/ticket/65054

Fixes #65054.

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown

Hi there! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@github-actions

github-actions Bot commented Jul 1, 2026 •

Copy link
Copy Markdown

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props manishxdp, mukesh27.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@mukeshpanchal27

Copy link
Copy Markdown
Member

Thanks, @manishdhorepatil-art, for the PR!

Instead of opening a separate PR, I think it would be better to review the existing PRs and share your thoughts or feedback there. That way, we can avoid reviewing multiple PRs for the same issue if only minor changes are needed.

@manishdhorepatil-art

Copy link
Copy Markdown
Author

@mukeshpanchal27

Thanks for the feedback

my intention was to align the change with the wordpress coding standards by sanitizing request data after calling wp_unslash(), since request superglobals are typically unslashed before sanitization in WordPress.

I understand your point about the existing PRs. rather than maintaining a duplicate PR, I'll review PR #11540 and PR #11661, share my feedback there, and close this PR if it's not needed.

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.

2 participants