CVE-2009-0829
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 QuoteBook allow remote attackers to execute arbitrary SQL commands via the (1) MyBox and (2) selectFavorites parameters to (a) quotes.php and the (3) QuoteName and (4) QuoteText parameters to (b) quotesadd.php. NOTE: the provenance of this information is unknown; the details are obtained solely 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 · moderate confidenceSQL injection vulnerabilities in QuoteBook PHP application allow remote attackers to execute arbitrary SQL commands. Vulnerable parameters include MyBox and selectFavorites in quotes.php, and QuoteName and QuoteText in quotesadd.php. The CVSS 7.5 score indicates high severity with network-exploitable, low-complexity attacks requiring no authentication.
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 dataall versionsCVSS 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.
-
Locate the QuoteBook application filesSearch the web root directory for files named quotes.php and quotesadd.php. These are the files containing the vulnerable code.Affected if The files quotes.php and/or quotesadd.php exist in the web-accessible directory.
-
Verify the application is network accessibleAttempt to access the quotes.php page via HTTP/HTTPS from a remote system or browser.Affected if The QuoteBook application is reachable over the network.
-
Identify if user input is accepted on vulnerable parametersExamine the quotes.php source code and look for the parameters 'MyBox' and 'selectFavorites' being used in SQL queries without proper escaping or prepared statements. Similarly, examine quotesadd.php for 'QuoteName' and 'QuoteText' parameters.Affected if The application processes user input through the parameters MyBox, selectFavorites, QuoteName, or QuoteText in dynamic SQL queries.
-
Confirm lack of parameterized queriesReview the source code in quotes.php and quotesadd.php. Search for use of PDO prepare(), mysqli_prepare(), or similar parameterized query functions. If the code directly concatenates or interpolates user input into SQL strings, the vulnerability exists.Affected if User-controlled parameters are concatenated directly into SQL queries without using prepared statements or parameter binding.
If the QuoteBook application files exist, are network-accessible, and process user input through MyBox, selectFavorites, QuoteName, or QuoteText parameters without parameterized queries, the environment is affected by this CVE.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) for all user-controlled inputs in quotes.php and quotesadd.php. Implement strict input validation and sanitize all parameters before database use.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0829 — 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-2009-0829 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