How severe is CVE-2006-3360?

No CVSS score has been assigned to CVE-2006-3360 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2006-3360?

CVE-2006-3360 affects the following packages: phpsysinfo/phpsysinfo (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2006-3360?

Update phpsysinfo/phpsysinfo to 3.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-3360 is resolved across your whole dependency graph.

How do I detect CVE-2006-3360 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpsysinfo/phpsysinfo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2006-3360 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2006-3360 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2006-3360, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2006-3360?

CVE-2006-3360 has an EPSS (Exploit Prediction Scoring System) score of 5.6%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2006-3360?

CVE-2006-3360 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2006-3360 published, and has it been updated?

CVE-2006-3360 was published on July 6, 2006 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2006-3360 — phpsysinfo

Fix: phpsysinfo/phpsysinfo@60b5bbb

CVE-2006-3360 is a Path Traversal vulnerability in phpsysinfo/phpsysinfo. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for phpsysinfo/phpsysinfo — see the affected versions and patch details below.

phpSysInfo allows remote attackers to determine the existence of arbitrary files via a .. (dot dot) sequence

Also known asGHSA-2wxv-3g4v-p76p

Published

Jul 6, 2006

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

5.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘phpsysinfo/phpsysinfo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Directory traversal vulnerability in index.php in phpSysInfo prior to 3.2.5 allows remote attackers to determine the existence of arbitrary files via a .. (dot dot) sequence and a trailing null (%00) byte in the lng parameter, which will display a different error message if the file exists.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpsysinfo/phpsysinfo`	all versions	3.2.5`composer require phpsysinfo/phpsysinfo:^3.2.5`

Affected Products

1 product · 1 configurations

Application

phpsysinfophpsysinfo

≤ 2.5.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Directory traversal vulnerability in index.php in phpSysInfo 2.5.1 allow…

archives.neohapsis.comNVDJul 2017

Report on archives.neohapsis.com

archives.neohapsis.comNVDJul 2017

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpsysinfo/phpsysinfo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update phpsysinfo/phpsysinfo to 3.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-3360 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-3360 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works