wppaste
WordPress

wp_set_password( string $password, int $user_id )

Since
2.5.0
Source
wp-includes/pluggable.php:2844
Updates the user's password with a new hashed one.

Description

For integration with other applications, this function can be overwritten to instead use the other package password checking algorithm.

Please note: This function should be used sparingly and is really only meant for single-time application. Leveraging this improperly in a plugin or theme could result in an endless loop of password resets if precautions are not taken to ensure it does not execute on every page load.

Compatibility

WordPress
since 2.5.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$passwordstring
The plaintext new user password.
$user_idint
User ID.

Performance profile

How much work a call to wp_set_password() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Heavy

Reaches the database via get_user_by().

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
31

Executed per call on PHP 8.5. The body compiles to 31.

Plugin surface
1 hook

Third-party callbacks on 'wp_set_password' run inside this call, and their cost is not bounded by anything here.

Called by
2

2 places in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksdo_action()called directly
  • querycontent queryget_user_by()one call below wp_set_password()
  • cacheobject cachewp_cache_delete()one call below wp_set_password()

What one call costs · 1 distinct outcome

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_set_password() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always31get_userdata(), wp_hash_password(), ID(), clean_user_cache(), do_action()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 31 instructions, 31 executed per call, 0 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Hooks and filters fired · 1

One hook fires while wp_set_password() runs, in this order:

  1. do_action( wp_set_password )actionline 2871 (+27 into the body)

    Fires after the user password is set.

Uses · 4

Used by · 2

Source code

	function wp_set_password( $password, $user_id ) {		global $wpdb; 		$old_user_data = get_userdata( $user_id ); 		$hash = wp_hash_password( $password );		$wpdb->update(			$wpdb->users,			array(				'user_pass'           => $hash,				'user_activation_key' => '',			),			array( 'ID' => $user_id )		); 		clean_user_cache( $user_id ); 		/**		 * Fires after the user password is set.		 *		 * @since 6.2.0		 * @since 6.7.0 The `$old_user_data` parameter was added.		 *		 * @param string  $password      The plaintext password just set.		 * @param int     $user_id       The ID of the user whose password was just set.		 * @param WP_User $old_user_data Object containing user's data prior to update.		 */		do_action( 'wp_set_password', $password, $user_id, $old_user_data );	}

Changelog

Introduced in 2.5.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 6.7.7 tag, from src/wp-includes/pluggable.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.