Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2006-1831: Direct static code injection vulnerability in sysinfo.cgi in sysinfo 1.21 and possibly other versions before 2

55
This week
HIGH 7.5DOWNGRADE

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

Direct static code injection vulnerability in sysinfo.cgi in sysinfo 1.21 and possibly other versions before 2.25 allows remote attackers to execute arbitrary commands via a leading ; (semicolon) in the name parameter in a systemdoc action, which is injected into phpinfo.php.

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.5% (top 5%)
CISA exploited listNo
Published2006-04-19
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: coder-world

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

coder-world sysinfo DOWNGRADE
Affected: 1.21
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.21
1. Check installed version
apt-cache policy sysinfo || rpm -q sysinfo || sysinfo --version
2. No fixed release: DOWNGRADE to a release before 1.21 (Debian / Ubuntu)
apt-cache madison sysinfo sudo apt install sysinfo=<VERSION_BEFORE_1.21> sudo apt-mark hold sysinfo
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sysinfo sudo dnf downgrade sysinfo-<VERSION_BEFORE_1.21> sudo dnf versionlock add sysinfo
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-2006-1831?

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

Is CVE-2006-1831 being exploited?

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

CVE-2006-1831 affects sysinfo. Severity is high (CVSS 7.5). Direct static code injection vulnerability in sysinfo.cgi in sysinfo 1.21 and possibly other versions before 2.25 allows remote attackers to execute arbitrary commands via a leading ; (semicolon) in the name parameter in a systemdoc action,

How urgent is CVE-2006-1831?

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

Software pages

PHP vulnerabilities

Related CVEs

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.