CVE-2007-5189
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 SQL injection vulnerabilities in mes_add.php in x-script GuestBook 1.3a, when magic_quotes_gpc is disabled, allow remote attackers to execute arbitrary SQL commands via the (1) name, (2) email, (3) icq, and (4) website parameters.
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 confidenceSQL injection in x-script GuestBook 1.3a's mes_add.php allows remote attackers to execute arbitrary SQL commands through the name, email, icq, and website parameters when magic_quotes_gpc is disabled. User input is not properly sanitized before being used in SQL queries.
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.3aCVSS 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 X Script Guestbook versionLocate the guestbook installation directory and identify the installed version by checking version files, headers, or the main index page for the version string '1.3a'Affected if The installed version is X Script Guestbook 1.3a
-
Locate the vulnerable scriptFind mes_add.php within the guestbook installation directory on the web serverAffected if mes_add.php exists in the guestbook directory and is accessible via the web server
-
Check PHP magic_quotes_gpc settingCreate a PHP info file (phpinfo.php) with content '<?php phpinfo(); ?>' and access it via browser, or check the PHP configuration directly for the magic_quotes_gpc valueAffected if magic_quotes_gpc is set to Off or disabled (the vulnerability only applies when this protection is off)
-
Inspect mes_add.php for SQL injection vulnerabilitiesOpen mes_add.php in a text editor and examine how the name, email, icq, and website parameters are used in SQL queries - look for direct insertion of these variables into SQL statements without proper escaping or parameterized queriesAffected if The parameters name, email, icq, or website are used directly in SQL queries without sanitization or prepared statements, and magic_quotes_gpc is disabled
You are affected if you have X Script Guestbook 1.3a running with magic_quotes_gpc disabled and the mes_add.php script handles user input from name, email, icq, or website parameters without sanitization.
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 dataImplement prepared statements/parameterized queries for all SQL queries using the affected parameters, and enable input validation. If magic_quotes_gpc is available, ensure it is enabled (note: this is deprecated in PHP 5.4+).
- Consultation1.0 h
- Implementation3.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5189 — 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-5189 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