CVE-2006-6267: PostNuke 0.7.5.0, and certain minor versions, allows remote attackers to obtain sensitive information via a no

This month

HIGH 7.8DOWNGRADE

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

PostNuke 0.7.5.0, and certain minor versions, allows remote attackers to obtain sensitive information via a non-numeric value of the stop parameter, which reveals the path in an error message.

Why this priority

High severity

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

Risk facts

CVSS score	7.8 (High)
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Published	2006-12-04
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: postnuke software foundation

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

Am I affected?

Timeline

2006-12-04 11:28 UTCPublished CVE record published
2026-06-16 22:32 UTCUpdated Record last modified

postnuke software foundation postnuke DOWNGRADE

Affected: 0.7.5.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.7.5.0

1. Check installed version

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

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

apt-cache madison postnuke sudo apt install postnuke=<VERSION_BEFORE_0.7.5.0> sudo apt-mark hold postnuke

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

dnf --showduplicates list postnuke sudo dnf downgrade postnuke-<VERSION_BEFORE_0.7.5.0> sudo dnf versionlock add postnuke

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.

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-6267?

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

Is CVE-2006-6267 being exploited?

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

CVE-2006-6267 affects postnuke. Severity is high (CVSS 7.8). PostNuke 0.7.5.0, and certain minor versions, allows remote attackers to obtain sensitive information via a non-numeric value of the stop parameter, which reveals the path in an error message.

How urgent is CVE-2006-6267?

Priority 45/100. High severity

Related CVEs

CVE-2010-1713 HIGH 7.5 DOWNGRADE SQL injection vulnerability in modules.php in PostNuke 0.764 allows remote attackers to execute arbitrary SQL
CVE-2008-1591 HIGH 7.5 UPGRADE The pnVarPrepForStore function in PostNuke 0.764 and earlier skips input sanitization when magic_quotes_runtim
CVE-2007-0386 HIGH 10.0 DOWNGRADE Unspecified vulnerability in the rating section in PostNuke 0.764 has unknown impact and attack vectors, relat
CVE-2007-0385 HIGH 7.8 DOWNGRADE The faq section in PostNuke 0.764 allows remote attackers to obtain sensitive information (the full path) via
CVE-2007-0384 MEDIUM 5.1 DOWNGRADE Cross-site scripting (XSS) vulnerability in preview in the reviews section in PostNuke 0.764 allows remote att

References

← Back to latest CVEs