CVE-2007-6348 json
SquirrelMail 1.4.11 and 1.4.12, as distributed on sourceforge.net before 20071213, has been externally modified to create a Trojan Horse th…
published 2007-12-14 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6315
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
SquirrelMail 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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2007-6348 updated
Squirrelmail compromise
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.91% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
secunia.com
/advisories/28095
third-party-advisory, vendor-advisory
-
marc.info
/?l=squirrelmail-devel&m=119765235203392&w=2
mailing-list
-
securityfocus.com
/archive/1/485037/100/0/threaded
mailing-list
-
marc.info
/?l=bugtraq&m=119765643909825&w=2
mailing-list
- squirrelmail.org /index.php
-
marc.info
/?l=squirrelmail-devel&m=119756462212214&w=2
mailing-list
-
osvdb.org
/42633
vdb-entry
Sources
- CVE List CVE-2007-6348
- NVD CVE-2007-6348
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.