WordPress before 2.6.2 does not properly handle MySQL warnings about insertion of username strings that exceed the maximum column width of the user_login column, and does not properly handle space characters when comparing usernames, which allows remote attackers to change an arbitrary user's password to a random value by registering a similar username and then requesting a password reset, related to a "SQL column truncation vulnerability." NOTE: the attacker can discover the random password by also exploiting CVE-2008-4107.
CVE-2008-4106 is a security vulnerability that . Impacting 1 product from wordpress organizations running these solutions should prioritize assessment and patching.
Originally identified in 2008, this vulnerability predates many modern security frameworks and practices. The vulnerability landscape of that era was characterized by different threat models and less mature defense mechanisms compared to contemporary standards.
2008-09-18T17:59:33.017
2026-04-23T00:35:47.467
Modified
CVSSv2: 5.1 (MEDIUM)
AV:N/AC:H/Au:N/C:P/I:P/A:P
4.9
6.4
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | wordpress | wordpress | ≤ 2.6.1 | Yes |
| Application | wordpress | wordpress | 0.71-gold | Yes |
| Application | wordpress | wordpress | 1.0-platinum | Yes |
| Application | wordpress | wordpress | 1.0.1-miles | Yes |
| Application | wordpress | wordpress | 1.0.2-blakey | Yes |
| Application | wordpress | wordpress | 1.2-delta | Yes |
| Application | wordpress | wordpress | 1.2-mingus | Yes |
| Application | wordpress | wordpress | 1.2.1 | Yes |
| Application | wordpress | wordpress | 1.2.2 | Yes |
| Application | wordpress | wordpress | 1.5-strayhorn | Yes |
| Application | wordpress | wordpress | 1.5.1.1 | Yes |
| Application | wordpress | wordpress | 1.5.1.2 | Yes |
| Application | wordpress | wordpress | 1.5.1.3 | Yes |
| Application | wordpress | wordpress | 1.5.2 | Yes |
| Application | wordpress | wordpress | 2.0 | Yes |
| Application | wordpress | wordpress | 2.0.1 | Yes |
| Application | wordpress | wordpress | 2.0.4 | Yes |
| Application | wordpress | wordpress | 2.0.5 | Yes |
| Application | wordpress | wordpress | 2.0.6 | Yes |
| Application | wordpress | wordpress | 2.0.7 | Yes |
| Application | wordpress | wordpress | 2.0.9 | Yes |
| Application | wordpress | wordpress | 2.0.10 | Yes |
| Application | wordpress | wordpress | 2.0.11 | Yes |
| Application | wordpress | wordpress | 2.1 | Yes |
| Application | wordpress | wordpress | 2.1.1 | Yes |
| Application | wordpress | wordpress | 2.1.2 | Yes |
| Application | wordpress | wordpress | 2.1.3 | Yes |
| Application | wordpress | wordpress | 2.2 | Yes |
| Application | wordpress | wordpress | 2.2.1 | Yes |
| Application | wordpress | wordpress | 2.2.2 | Yes |
| Application | wordpress | wordpress | 2.2.3 | Yes |
| Application | wordpress | wordpress | 2.5 | Yes |
| Application | wordpress | wordpress | 2.5.1 | Yes |
| Application | wordpress | wordpress | 2.6 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For wordpress's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.