CVE-2002-1748: Unknown vulnerability in Slash 2.1.x and 2.2 through 2.2.2, as used in Slashcode, allows remote authenticated

Routine

HIGH 7.2DOWNGRADE

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

Unknown vulnerability in Slash 2.1.x and 2.2 through 2.2.2, as used in Slashcode, allows remote authenticated users to gain access to arbitrary accounts.

Why this priority

High severity

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

Risk facts

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

Publisher (CNA): MITRE · Vendor: open source development network

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

open source development network slashcode DOWNGRADE

Affected: 2.1 · 2.1.1 · 2.2 · 2.2.1 · 2.2.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1

1. Check installed version

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

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

apt-cache madison slashcode sudo apt install slashcode=<VERSION_BEFORE_2.1> sudo apt-mark hold slashcode

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

dnf --showduplicates list slashcode sudo dnf downgrade slashcode-<VERSION_BEFORE_2.1> sudo dnf versionlock add slashcode

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

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

Is CVE-2002-1748 being exploited?

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

CVE-2002-1748 affects slashcode. Severity is high (CVSS 7.2). Unknown vulnerability in Slash 2.1.x and 2.2 through 2.2.2, as used in Slashcode, allows remote authenticated users to gain access to arbitrary accounts.

How urgent is CVE-2002-1748?

Priority 39/100. High severity

Related CVEs

CVE-2004-2656 MEDIUM 4.3 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in Slashdot Like Automated Storytelling Homepage (Slash) (
CVE-2002-1681 MEDIUM 6.8 DOWNGRADE Cross-site scripting (XSS) vulnerability in Slashcode CVS releases June 17 through July 1 2002 allows remote a
CVE-2002-0292 LOW 2.6 UPGRADE Cross-site scripting vulnerability in Slash before 2.2.5, as used in Slashcode and elsewhere, allows remote at
CVE-2001-1535 MEDIUM 4.6 DOWNGRADE Slashcode 2.0 creates new accounts with an 8-character random password, which could allow local users to obtai
CVE-2000-1015 HIGH 7.5 UPGRADE The default configuration of Slashcode before version 2.0 Alpha has a default administrative password, which a

References

← Back to latest CVEs