CVE-2006-6861: Multiple SQL injection vulnerabilities in Outfront Spooky Login 2.7 allow remote attackers to execute arbitrar

This month

HIGH 10.0DOWNGRADE

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

Multiple SQL injection vulnerabilities in Outfront Spooky Login 2.7 allow remote attackers to execute arbitrary SQL commands via (1) the UserUpdate parameter to login/register.asp or (2) unspecified parameters to includes/a_register.asp.

Why this priority

Critical severity
Public exploit reference

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

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Published	2006-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

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

outfront spooky login DOWNGRADE

Affected: 2.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.7

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.7 (Debian / Ubuntu)

apt-cache madison spooky-login sudo apt install spooky-login=<VERSION_BEFORE_2.7> 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.7> 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: Spooky 2.7 - 'login/register.asp' SQL Injection

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-2006-6861?

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

Is CVE-2006-6861 being exploited?

CVE-2006-6861 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-2006-6861 affect?

CVE-2006-6861 affects spooky login. Severity is high (CVSS 10.0). Multiple SQL injection vulnerabilities in Outfront Spooky Login 2.7 allow remote attackers to execute arbitrary SQL commands via (1) the UserUpdate parameter to login/register.asp or (2) unspecified parameters to includes/a_register.asp.

How urgent is CVE-2006-6861?

Priority 58/100. Critical 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-2002-1720 HIGH 7.5 DOWNGRADE SQL injection vulnerability in Spooky Login 2.0 through 2.5 allows remote attackers to bypass authentication a

References

← Back to latest CVEs