CVE-2002-1952
phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating...
phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which could allow remote attackers to authenticate using a NULL password when database errors occur or if the database is unavailable.
Exploit likelihood
What each source reports
NVD Score used
phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which could allow remote attackers to authenticate using a NULL password when database errors occur or if the database is unavailable.
- Record
CVE-2002-1952- CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Updated
- 2026-11-02
CVE List No score
phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which could allow remote attackers to authenticate using a NULL password when database errors occur or if the database is unavailable.
- Record
CVE-2002-1952- Updated
- 2026-11-02
EUVDEUVD-2002-1931 No score
phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which could allow remote attackers to authenticate using a NULL password when database errors occur or if the database is unavailable.
- Record
EUVD-2002-1931- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-f5v8-cx94-qh2x No score
phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating...
phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which could allow remote attackers to authenticate using a NULL password when database errors occur or if the database is unavailable.
- Record
GHSA-f5v8-cx94-qh2x- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2002-1952 is a high vulnerability (CVSS 7.5) in Phprank, published December 31, 2002. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.57%, the 75th percentile. No source names a fixed version.