CVE-2001-0113: statsconfig.pl in OmniHTTPd 2.07 allows remote attackers to execute arbitrary commands via the mostbrowsers pa

This week

HIGH 10.0DOWNGRADE

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

statsconfig.pl in OmniHTTPd 2.07 allows remote attackers to execute arbitrary commands via the mostbrowsers parameter, whose value is used as part of a generated Perl script.

Why this priority

Critical severity
EPSS top 4%: very likely to be exploited
Public exploit reference

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

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	10.4% (top 4%)
CISA exploited list	No
Published	2001-03-12
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: omnicron

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

Am I affected?

Timeline

2001-03-12 05:00 UTCPublished CVE record published
2026-06-16 21:53 UTCUpdated Record last modified

omnicron omnihttpd DOWNGRADE

Affected: 2.0.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.7

1. Check installed version

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

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

apt-cache madison omnihttpd sudo apt install omnihttpd=<VERSION_BEFORE_2.0.7> sudo apt-mark hold omnihttpd

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

dnf --showduplicates list omnihttpd sudo dnf downgrade omnihttpd-<VERSION_BEFORE_2.0.7> sudo dnf versionlock add omnihttpd

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: Omnicron OmniHTTPd 2.0.7 - File Corruption / Command Execution

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-2001-0113?

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

Is CVE-2001-0113 being exploited?

CVE-2001-0113 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-2001-0113 affect?

CVE-2001-0113 affects omnihttpd. Severity is high (CVSS 10.0). statsconfig.pl in OmniHTTPd 2.07 allows remote attackers to execute arbitrary commands via the mostbrowsers parameter, whose value is used as part of a generated Perl script.

How urgent is CVE-2001-0113?

Priority 64/100. Critical severity; EPSS top 4%: very likely to be exploited; Public exploit reference

Software pages

Perl vulnerabilities

Related CVEs

CVE-2002-1455 MEDIUM 4.3 MITIGATE Multiple cross-site scripting (XSS) vulnerabilities in OmniHTTPd allow remote attackers to insert script or HT
CVE-2002-1035 MEDIUM 5.0 DOWNGRADE Omnicron OmniHTTPd 2.09 allows remote attackers to cause a denial of service (crash) via an HTTP request with
CVE-2001-0778 MEDIUM 5.0 UPGRADE OmniHTTPd 2.0.8 and earlier allow remote attackers to obtain source code via a GET request with the URL-encode
CVE-2001-0777 MEDIUM 5.0 DOWNGRADE Omnicron OmniHTTPd 2.0.8 allows remote attackers to cause a denial of service (memory exhaustion) via a series
CVE-2001-0613 MEDIUM 5.0 UPGRADE Omnicron Technologies OmniHTTPD Professional 2.08 and earlier allows a remote attacker to create a denial of s

References

← Back to latest CVEs