Wordpress v2.6.0/2.6.1 Hash

Technical details, regex signatures, and cracking commands for the Wordpress v2.6.0/2.6.1 algorithm.

Regex Identification Signature:
^\$H\$[a-z0-9\/.]{31}$
Hashcat Command (Mode: 400):
John the Ripper Command:
← Back to Hash Identifier

What is Wordpress v2.6.0/2.6.1?

The WordPress v2.6.0/2.6.1 hash format is a legacy password hashing scheme introduced in WordPress versions 2.6.0 and 2.6.1, predating the adoption of stronger cryptographic practices. This format encodes passwords using a combination of MD5-based hashing and a simple base64 encoding scheme, structured as `$P$`. The salt is a 22-character string derived from the password and a static prefix, but it is not cryptographically secure—it is generated as `salt = md5(md5(password) . $P$ . rand())`, where `.` denotes concatenation and `rand()` produces a pseudo-random number. The final hash is computed as `md5(md5(password) . $salt)`, and the result is base64-encoded before storage. This scheme was designed for simplicity and compatibility with existing systems but lacks modern cryptographic rigor, relying on a flawed salt implementation and weak hashing iteration.

The WordPress v2.6.0/2.6.1 hash format is highly vulnerable to cracking due to its reliance on MD5, a cryptographically broken hash function susceptible to rainbow table attacks and collision exploits. The absence of a proper salt (the pseudo-random component is predictable and derived from the password itself) reduces entropy, enabling offline brute-force attacks. Additionally, the single MD5 iteration provides negligible computational resistance, allowing modern GPU-accelerated tools (e.g., Hashcat or John the Ripper) to crack hashes at high speeds—often within minutes or hours. The lack of key stretching or iterative hashing further exacerbates this, as adversaries can exploit optimized hardware to test millions of passwords per second, rendering the format unsuitable for secure password storage.

Identifying Wordpress v2.6.0/2.6.1 Hashes

Identifying a hash blindly is often difficult because multiple algorithms can output strings of the exact same length. For example, a standard 32-character hexadecimal string could be MD5, NTLM, MD4, or LM. To definitively identify Wordpress v2.6.0/2.6.1, security researchers analyze the hash against a strict regular expression (regex) signature (shown above) to find structural matches.

How to Crack Wordpress v2.6.0/2.6.1

If you need to recover the plaintext password for a Wordpress v2.6.0/2.6.1 hash during a penetration test or forensics investigation, you must supply the correct module ID to your cracking software. Use the exact commands provided at the top of this page to target the hash successfully.