dbcve.org
Der DirigentApplication

CVE-2007-5146

MEDIUM · 6.8 CVSS v2.0 Published 2007-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Multiple PHP remote file inclusion vulnerabilities in dedi-group Der Dirigent 1.0 allow remote attackers to execute arbitrary PHP code via a URL in the dedi_path parameter to (1) inc.generate_code.php, (2) fnc.type_forms.php, or (3) fnc.type.php in backend/inc/, or (4) frontend.php or (5) backend.php in projekt01/cms/inc/; or (6) the this_dir parameter to backend/inc/class.filemanager.php. NOTE: vectors 4 and 5 are disputed by CVE because PHP encounters a fatal function-call error on a direct request for the file, before reaching the include statement.

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 confidence

Der Dirigent 1.0 contains multiple PHP remote file inclusion vulnerabilities where user-supplied input from the dedi_path and this_dir parameters is directly used in include() statements without sanitization. An attacker can supply a malicious URL pointing to remote PHP code that will be executed on the target server.

MitigationRemediate by removing or hardening the vulnerable include() statements in affected backend/inc/ and projekt01/cms/inc/ files—implement strict allowlist-based input validation or use defined constants for include paths rather than user-controlled parameters.

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
Der DirigentApplication
Affected:= 1.0

CVSS 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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Der Dirigent installation
    Search the web server document root for directories or files containing 'Der Dirigent' or 'derdirigent' naming patterns. Look for PHP files that are part of this application.
    Affected if Der Dirigent version 1.0 is found on the server
  2. Confirm version number
    Check the application's main PHP file, readme, or any version file for the exact version string. Compare against the affected version = 1.0.
    Affected if Installed version is Der Dirigent 1.0
  3. Identify vulnerable backend/inc/ files
    Examine PHP files in the backend/inc/ directory for include() statements that use the 'dedi_path' parameter without sanitization, for example: include($dedi_path . '/file.php')
    Affected if Files contain include() statements using unsanitized dedi_path parameter
  4. Identify vulnerable projekt01/cms/inc/ files
    Examine PHP files in the projekt01/cms/inc/ directory for include() statements that use the 'this_dir' parameter without sanitization, for example: include($this_dir . '/file.php')
    Affected if Files contain include() statements using unsanitized this_dir parameter
  5. Verify parameter accessibility
    Test if the application accepts and processes GET or POST parameters named 'dedi_path' or 'this_dir' through the affected PHP scripts without validation.
    Affected if The vulnerable parameters are directly used in include() calls without input filtering

A server is affected if Der Dirigent 1.0 is installed and contains PHP files in backend/inc/ or projekt01/cms/inc/ that use unsanitized dedi_path or this_dir parameters in include() statements, allowing remote file inclusion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remediate by removing or hardening the vulnerable include() statements in affected backend/inc/ and projekt01/cms/inc/ files—implement strict allowlist-based input validation or use defined constants for include paths rather than user-controlled parameters.

Fix this in Der Dirigent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-5146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-5146 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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