CVE-2002-1720: SQL injection vulnerability in Spooky Login 2.0 through 2.5 allows remote attackers to bypass authentication a

This month

HIGH 7.5DOWNGRADE

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

SQL injection vulnerability in Spooky Login 2.0 through 2.5 allows remote attackers to bypass authentication and gain privileges via the password field.

Why this priority

High severity
Public exploit reference

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

Risk facts

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

Publisher (CNA): MITRE · Vendor: outfront

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 21:59 UTCUpdated Record last modified

outfront spooky login DOWNGRADE

Affected: 2.0 · 2.1 · 2.2 · 2.3 · 2.4 · 2.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0

1. Check installed version

apt-cache policy spooky-login || rpm -q spooky-login || spooky-login --version

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

apt-cache madison spooky-login sudo apt install spooky-login=<VERSION_BEFORE_2.0> sudo apt-mark hold spooky-login

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

dnf --showduplicates list spooky-login sudo dnf downgrade spooky-login-<VERSION_BEFORE_2.0> sudo dnf versionlock add spooky-login

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Outfront Spooky 2.x - Login SQL Query Manipulation Password

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-1720?

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

Is CVE-2002-1720 being exploited?

CVE-2002-1720 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-1720 affect?

CVE-2002-1720 affects spooky login. Severity is high (CVSS 7.5). SQL injection vulnerability in Spooky Login 2.0 through 2.5 allows remote attackers to bypass authentication and gain privileges via the password field.

How urgent is CVE-2002-1720?

Priority 53/100. High severity; Public exploit reference

Related CVEs

CVE-2006-6862 MEDIUM 6.8 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in Outfront Spooky Login 2.7 allow remote attackers to inj
CVE-2006-6861 HIGH 10.0 DOWNGRADE Multiple SQL injection vulnerabilities in Outfront Spooky Login 2.7 allow remote attackers to execute arbitrar

References

← Back to latest CVEs