CVE-2007-6138
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 · uneditedSQL injection vulnerability in redir.asp in VU Mass Mailer allows remote attackers to execute arbitrary SQL commands via the password parameter to Default.asp (aka the Login Page). NOTE: some of these details are obtained 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 vulnerability in the VU Mass Mailer application where the password parameter on the login page (Default.asp/redir.asp) fails to properly sanitize user input, allowing remote attackers to inject arbitrary SQL commands.
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.
-
Confirm VU Mass Mailer installationSearch the web server filesystem for files named 'Default.asp' or 'redir.asp' that are part of the VU Mass Mailer application. Check common web root directories such as /inetpub/wwwroot/, /var/www/, or the application's specific directory.Affected if VU Mass Mailer application files (Default.asp or redir.asp) are found on the server
-
Identify application versionExamine the application directory for version information in files such as version.txt, about.asp, or any readme/install files. Also check the HTTP headers or any banner information when accessing the login page.Affected if Any version of VU Mass Mailer is identified (all versions are affected)
-
Verify login page accessibilityAttempt to access the login page via HTTP/HTTPS. The vulnerable pages are typically at paths like /Default.asp or /redir.asp within the VU Mass Mailer directory.Affected if The login page (Default.asp or redir.asp) is accessible over the network
-
Review code for SQL injection susceptibilityExamine the source code of Default.asp or redir.asp, specifically looking for SQL query construction that uses the password parameter without parameterized queries. Search for string concatenation or dynamic SQL building involving request variables for passwords.Affected if The code shows direct insertion of password parameter into SQL queries without input sanitization or parameterized queries
The environment is affected if VU Mass Mailer is installed and the login page (Default.asp or redir.asp) handles the password parameter without parameterized queries or input 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 parameterized queries (prepared statements) for all database interactions, particularly the login query. Alternatively, implement strict input validation and escaping for the password parameter. As a temporary measure, consider deploying a web application firewall.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6138 — 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-6138 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