CVE-2007-2997
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 cgi-bin/reorder2.asp in SalesCart Shopping Cart allow remote attackers to execute arbitrary SQL commands via the password field and other unspecified vectors. NOTE: the vendor disputes this issue, stating "We were able to reproduce this sql injection on an old out-of-date demo on the website but not on the released product.
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 vulnerabilities in SalesCart Shopping Cart's reorder2.asp script allow remote attackers to inject arbitrary SQL commands via the password field and other parameters. This authentication bypass enables attackers to execute database operations without valid credentials.
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.
-
Identify SalesCart Shopping Cart installationSearch web servers for files named 'reorder2.asp' or 'SalesCart' related files. Check website directories for the presence of SalesCart shopping cart software.Affected if SalesCart Shopping Cart software is found on the system
-
Locate the vulnerable reorder2.asp scriptSearch the web root directory for the file 'reorder2.asp' - this is the specific script containing the SQL injection vulnerability.Affected if The file reorder2.asp exists in the web application directory
-
Verify the application handles user credentialsExamine the reorder2.asp script to confirm it processes a password field and other user-supplied parameters for authentication or order processing.Affected if The script accepts and processes a password parameter without parameterized queries
-
Check application accessibilityDetermine if the reorder2.asp endpoint is accessible from the network (verify the web application is exposed and not behind a firewall that blocks external access).Affected if The vulnerable script is reachable over the network without authentication requirements
-
Confirm SQL query construction in the scriptReview the reorder2.asp source code to identify if SQL queries are constructed using string concatenation with user input rather than parameterized queries or prepared statements.Affected if User-supplied input from the password field is directly concatenated into SQL queries without sanitization or parameterization
The environment is affected if SalesCart Shopping Cart with the reorder2.asp script is installed and accessible, as all versions contain the SQL injection vulnerability in the password field handling.
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 dataUpgrade to current shopping cart software with parameterized queries, or if unsupported, implement input validation and stored procedures at the database layer to neutralize SQL injection vectors.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2997 — 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-2997 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