CVE-2006-5720
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL injection vulnerability in modules/journal/search.php in the Journal module in Francisco Burzi PHP-Nuke 7.9 and earlier allows remote attackers to execute arbitrary SQL commands via the forwhat parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the Journal module's search.php allows remote attackers to execute arbitrary SQL commands via the forwhat parameter in PHP-Nuke 7.9 and earlier.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7.9= 7.0= 7.1= 7.2= 7.3= 7.4= 7.5= 7.6= 7.7= 7.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PHP-Nuke installationLook for typical PHP-Nuke directories such as /modules/, /includes/, or /admin/ on your web server. Check for the presence of index.php with PHP-Nuke branding or configuration files like config.php in the web root.Affected if PHP-Nuke software is present on the server
-
Determine PHP-Nuke versionOpen the main config.php file in the web root and look for a variable that holds the version number (often named $Version or similar), or access the admin panel and view the system information page.Affected if The installed version is 7.9 or any version 7.0 through 7.8 (versions <= 7.9)
-
Locate Journal moduleCheck for the existence of the Journal module directory at /modules/Journal/ on the web server. Verify if search.php exists within that directory.Affected if The modules/Journal/search.php file exists on the server
-
Verify Journal module is activeCheck the PHP-Nuke modules administration panel to confirm whether the Journal module is listed as active, or inspect the modules table in the database if you have access.Affected if The Journal module is enabled or installed in PHP-Nuke
You are affected if you have PHP-Nuke version 7.9 or earlier (7.0-7.8) AND the Journal module with its search.php file is present and enabled on your server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEither upgrade to a patched PHP-Nuke version or disable the Journal module; alternatively, implement proper input validation and use parameterized queries for the forwhat parameter.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5720 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-5720 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data