Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2005-0316: WebWasher Classic 2.2.1 and 3.3, when running in server mode, does not properly drop CONNECT requests to the l

55
This month
HIGH 7.5DOWNGRADE

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

WebWasher Classic 2.2.1 and 3.3, when running in server mode, does not properly drop CONNECT requests to the localhost from external systems, which could allow remote attackers to bypass intended access restrictions.

Why this priority

  • High severity
  • EPSS top 5%: very likely to be exploited
  • Public exploit reference

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

Risk facts

CVSS score7.5 (High)
EPSS exploit chance8.2% (top 5%)
CISA exploited listNo
Published2005-01-28
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: webwasher

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

webwasher webwasher classic DOWNGRADE
Affected: 2.2.1 · 3.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.2.1
1. Check installed version
apt-cache policy webwasher-classic || rpm -q webwasher-classic || webwasher-classic --version
2. No fixed release: DOWNGRADE to a release before 2.2.1 (Debian / Ubuntu)
apt-cache madison webwasher-classic sudo apt install webwasher-classic=<VERSION_BEFORE_2.2.1> sudo apt-mark hold webwasher-classic
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list webwasher-classic sudo dnf downgrade webwasher-classic-<VERSION_BEFORE_2.2.1> sudo dnf versionlock add webwasher-classic
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.

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-2005-0316?

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

Is CVE-2005-0316 being exploited?

CVE-2005-0316 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-2005-0316 affect?

CVE-2005-0316 affects webwasher classic. Severity is high (CVSS 7.5). WebWasher Classic 2.2.1 and 3.3, when running in server mode, does not properly drop CONNECT requests to the localhost from external systems, which could allow remote attackers to bypass intended access restrictions.

How urgent is CVE-2005-0316?

Priority 55/100. High severity; EPSS top 5%: very likely to be exploited; Public exploit reference

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.