Use wp_rand() for multisite admin email confirmation token generation

[tanjiroK-coder]

Replace mt_rand() with wp_rand() when generating the confirmation token in update_network_option_new_admin_email().

This aligns multisite behavior with the security hardening previously applied to similar email-change confirmation flows in core.

Background

The confirmation token is currently generated using:

md5( $value . time() . mt_rand() );

While the token includes additional inputs, mt_rand() is not intended for security-sensitive randomness.

WordPress previously hardened similar email-change confirmation token generation by replacing mt_rand() with wp_rand() in:

• update_option_new_admin_email()
• send_confirmation_on_profile_email()

This change applies the same approach to the multisite/network equivalent function, ensuring consistency across all email-change confirmation workflows.

Changes

- $hash = md5( $value . time() . mt_rand() );
+ $hash = md5( $value . time() . wp_rand() );

Testing

• Confirmed the admin email change workflow continues to generate and validate confirmation tokens correctly.
• Verified no syntax errors.
• Verified wp_rand() is available when the hook executes.
• Existing token verification logic remains unchanged.

[github-actions]

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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @tanjiroK-coder.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

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

Props apermo.

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

[github-actions]

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:

• PHP Coding Standards
• CSS Coding Standards
• HTML Coding Standards
• JavaScript Coding Standards
• Accessibility Coding Standards
• Inline Documentation Standards

Thank you,
The WordPress Project

[apermo]

LGTM

[tanjiroK-coder]

any update on this?

[apermo]

Hey @tanjiroK-coder I cannot progress this any further, what would help is a related trac ticket, as this would actually help the progress.

There might be an umbrella ticket for general modernization.

cc @westonruter