dbcve.org
Guestbook ScriptApplication · Stadtaus

CVE-2007-4290

CRITICAL · 9.8 CVSS v3.1 Published 2007-08-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Guestbook Script 1.9 allow remote attackers to execute arbitrary PHP code via a URL in the script_root parameter to (1) delete.php, (2) edit.php, or (3) inc/common.inc.php; or (4) database.php, (5) entries.php, (6) index.php, (7) logout.php, or (8) settings.php in admin/. NOTE: a third party disputes this vulnerability, noting that these scripts defend against direct requests

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

Remote File Inclusion (RFI) vulnerability in Guestbook Script 1.9 allows remote attackers to execute arbitrary PHP code by supplying a malicious URL via the unsanitized script_root parameter in multiple PHP files including delete.php, edit.php, inc/common.inc.php, and admin/ directory files. This is a pre-authentication flaw enabling complete system compromise.

MitigationUpgrade to a patched version of Guestbook Script; if unavailable, remove the software entirely. As a temporary measure, disable PHP include/require for user-supplied parameters or implement strict input validation on the script_root parameter.

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
Guestbook ScriptApplication
Affected:= 1.9

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Guestbook Script installation files
    Search the web server document root for directories containing the affected PHP files: delete.php, edit.php, inc/common.inc.php, and files under the admin/ subdirectory. Also look for readme.txt, install.php, or version information files.
    Affected if Stadtaus Guestbook Script files are present on the server.
  2. Determine installed version
    Open any version file, readme, or the main PHP entry point in the guestbook directory. Look for a version string or number. Compare this to the affected version 1.9.
    Affected if The installed version is exactly 1.9.
  3. Verify PHP is enabled on the web server
    Check if PHP is an enabled handler for .php files in the web server configuration (httpd.conf, .htaccess, or nginx config). Confirm the guestbook scripts can be executed as PHP.
    Affected if PHP is enabled and the guestbook scripts are executable.
  4. Confirm web accessibility
    Attempt to access one of the affected PHP files (delete.php or edit.php) via HTTP from an external client or verify the web server is serving the guestbook directory to network clients.
    Affected if The guestbook application is accessible over the network without authentication.
  5. Inspect script_root parameter handling
    Examine the source code of inc/common.inc.php and other affected files for the script_root parameter usage. Verify it is not sanitized before being used in include/require statements.
    Affected if The script_root parameter can be controlled by user input and is used in include/require without sanitization.

The environment is affected if Stadtaus Guestbook Script version 1.9 is installed, PHP is enabled, and the application is web-accessible with an unsanitized script_root parameter in the affected files.

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 a patched version of Guestbook Script; if unavailable, remove the software entirely. As a temporary measure, disable PHP include/require for user-supplied parameters or implement strict input validation on the script_root parameter.

Fix this in Guestbook Script Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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