CVE-2006-5507
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 · uneditedMultiple PHP remote file inclusion vulnerabilities in Der Dirigent (DeDi) 1.0.3 allow remote attackers to execute arbitrary PHP code via a URL in the cfg_dedi[dedi_path] parameter in (1) find.php, (2) insert_line.php, (3) fullscreen.php, (4) changecase.php, (5) insert_link.php, (6) insert_table.php, (7) table_cellprop.php, (8) table_prop.php, (9) table_rowprop.php, (10) insert_page.php, and possibly insert_marquee.php in backend/external/wysiswg/popups/.
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 confidenceDer Dirigent (DeDi) 1.0.3 contains multiple PHP files in backend/external/wysiswg/popups/ that allow remote file inclusion via the cfg_dedi[dedi_path] parameter. An attacker can supply a malicious URL causing the application to include and execute arbitrary PHP code from a remote source.
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= 1.0.3CVSS 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 Der Dirigent installationLocate the DeDi application on the server and check its version number, typically found in an index file, README, or version constant within the PHP source codeAffected if The installed version is Der Dirigent 1.0.3 exactly
-
Verify vulnerable path existsCheck for the presence of the directory backend/external/wysiswg/popups/ within the DeDi web root and list its PHP filesAffected if This directory and its PHP files are present on the server
-
Inspect vulnerable parameter usageOpen the PHP files in backend/external/wysiswg/popups/ and search for occurrences of cfg_dedi[dedi_path] to see if the application uses this array key in include or require statements without validationAffected if The code uses cfg_dedi[dedi_path] in include/require statements without sanitizing the input
-
Confirm parameter is user-controllableReview how cfg_dedi[dedi_path] receives its value - check if it comes from $_GET, $_POST, or a configuration file that can be modifiedAffected if The parameter can be set via HTTP request (GET/POST) or loaded from an editable configuration
-
Test for external URL inclusion capabilityAttempt a controlled test (if safe to do so) or review php.ini to see if allow_url_include is enabled, which permits including files from remote URLsAffected if The PHP environment has allow_url_include enabled and the vulnerable code path is accessible
A server is affected if it runs Der Dirigent 1.0.3 with the backend/external/wysiswg/popups/ files present and the cfg_dedi[dedi_path] parameter is used in include statements without validation.
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 allow_url_include and allow_url_fopen in php.ini, then audit and fix all listed files to validate or hardcode the cfg_dedi[dedi_path] path instead of accepting user-controlled input.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5507 — 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-5507 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