CVE-2007-6348
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 · uneditedSquirrelMail 1.4.11 and 1.4.12, as distributed on sourceforge.net before 20071213, has been externally modified to create a Trojan Horse that introduces a PHP remote file inclusion vulnerability, which allows remote attackers to execute arbitrary code.
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 confidenceSquirrelMail versions 1.4.11 and 1.4.12 distributed via SourceForge before December 13, 2007 were trojanized by attackers. The downloaded packages contained a PHP remote file inclusion vulnerability that was externally introduced, allowing remote attackers to execute arbitrary code by including malicious remote files.
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.4.11= 1.4.12CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 installed SquirrelMail versionLocate the version file or index.php and read the version string (typically shows '1.4.11' or '1.4.12')Affected if Version is 1.4.11 or 1.4.12
-
Determine source acquisition dateCheck file timestamps, download logs, or archive metadata for when the SquirrelMail package was obtainedAffected if Package was downloaded before December 13, 2007 from the compromised SourceForge distribution
-
Inspect PHP files for remote include statementsSearch all .php files for include(), require(), include_once(), or require_once() calls with http:// or https:// URLs as parametersAffected if Any PHP file contains remote URL includes pointing to external domains
-
Check for suspicious encoded stringsSearch PHP source for base64_decode(), eval(), or similar code execution functions in combination with variable strings that appear obfuscatedAffected if Suspicious encoded payloads or dynamic code execution patterns are found in PHP files
A user is affected if they have SquirrelMail version 1.4.11 or 1.4.12 that was obtained from SourceForge before December 13, 2007, or if their installation contains remote file inclusion code in PHP files.
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 dataVerify any historical installations of SquirrelMail 1.4.11/1.4.12 were obtained after 20071213; replace with clean versions from trusted sources and audit for unauthorized include() or require() statements pointing to remote resources.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6348 — 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-6348 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