# CVE-2006-1831: Direct static code injection vulnerability in sysinfo.cgi in sysinfo 1.21 and possibly other versions before 2.25 allows remote attackers to


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xm97-7rvr-ppc2

## What is CVE-2006-1831?

CVE-2006-1831 is a high-severity vulnerability in n/a, published on 19 Apr 2006. 

### Official description

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.

## Which versions are affected by CVE-2006-1831?

It affects 1 product.


Products: Coder-World Sysinfo.

## How do I fix CVE-2006-1831?

No fix has been published for CVE-2006-1831 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-1831 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1831 exists.

Public exploit code:

- SysInfo 1.21 - 'sysinfo.cgi' Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1832](https://insights.sbomify.com/CVE-2006-1832/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1831 and fix it if it is affected.

What it is: CVE-2006-1831 is a high-severity vulnerability in n/a, published on 19 Apr 2006. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-1831 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-1831/ (Markdown: https://insights.sbomify.com/CVE-2006-1831/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-1831
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-1831
- OSV: https://osv.dev/vulnerability/CVE-2006-1831

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-1831/
Summaries are generated and may contain mistakes; the official description above is the record.