CVE-2002-1952: phpRank 1.8 does not properly check the return codes for MySQL operations when authenticating users, which cou

This month

HIGH 7.5WATCHLISTDOWNGRADE

CVE-2002-1952 is a high-severity flaw (CVSS 7.5) affecting phprank. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.6% (top 25%)
CISA exploited list	No
Published	2002-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: phprank

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2002-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:00 UTCUpdated Record last modified

phprank phprank DOWNGRADE

Affected: 1.8

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.8

1. Check installed version

apt-cache policy phprank || rpm -q phprank || phprank --version

2. No fixed release: DOWNGRADE to a release before 1.8 (Debian / Ubuntu)

apt-cache madison phprank sudo apt install phprank=<VERSION_BEFORE_1.8> sudo apt-mark hold phprank

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list phprank sudo dnf downgrade phprank-<VERSION_BEFORE_1.8> sudo dnf versionlock add phprank

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2002-1952?

phprank: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-1952 being exploited?

CVE-2002-1952 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2002-1952 affect?

CVE-2002-1952 affects phprank. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2002-1952?

Priority 50/100. High severity; On your watchlist

Software pages

MySQL vulnerabilities

Related CVEs

CVE-2002-1950 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in phpRank 1.8 allows remote attackers to inject arbitrary web script
CVE-2002-1800 HIGH 7.5 DOWNGRADE phpRank 1.8 stores the administrative password in plaintext on the server and in the "ap" cookie, which allows
CVE-2002-1799 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in phpRank 1.8 allows remote attackers to inject arbitrary web script

References

← Back to latest CVEs