CVE-2006-5431
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 · uneditedPHP remote file inclusion vulnerability in gorum/dbproperty.php in PHPOutsourcing Zorum 3.5 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the appDirName 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 confidenceRemote file inclusion vulnerability in Zorum 3.5 and earlier allows arbitrary PHP code execution through the unsanitized appDirName parameter passed to gorum/dbproperty.php, enabling attackers to include malicious remote files.
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<= 3.5CVSS 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.
-
Confirm Zorum installationLook for Zorum web application files in the web root directory, typically in a folder named 'zorum' or 'Zorum', or check for files containing 'Zorum' branding in the application.Affected if Zorum phpoutsourcing software is present on the server.
-
Identify installed Zorum versionLocate and read the version file or any version indicator within the Zorum installation. Common locations include a version.php file, README file, or the main index.php header/comments showing version information.Affected if The installed version is 3.5 or any version numbered lower than 3.5.
-
Verify vulnerable file existsCheck for the presence of the file gorum/dbproperty.php within the Zorum installation directory.Affected if The file gorum/dbproperty.php exists and is accessible via web requests.
-
Check if parameter is reachableTest accessing the vulnerable script directly via HTTP request to gorum/dbproperty.php with a test value for the appDirName parameter, such as: /path/to/zorum/gorum/dbproperty.php?appDirName=testAffected if The script responds and accepts the appDirName parameter without proper validation or restrictions.
-
Review PHP allow_url_include settingCheck the PHP configuration file (php.ini) or use phpinfo() to determine if allow_url_include is enabled.Affected if allow_url_include is set to On, allowing remote file inclusions through the vulnerable parameter.
You are affected if Zorum version 3.5 or lower is installed, the gorum/dbproperty.php file exists, and the appDirName parameter is processed without sanitization.
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 dataDisable PHP's allow_url_include setting, implement strict input validation on the appDirName parameter to restrict it to local paths only, and upgrade to a patched version if available.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5431 — 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-5431 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