Skip to content
Noroxi
CVE-2006-6142· NVD / CVE Program· CNA mitre

Multiple cross-site scripting (XSS) vulnerabilities in SquirrelMail 1.4.0 through 1.4.9 allow remote attackers to inject arbitrary web scrip

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.3% (FIRST EPSS); higher than 83.5% of all records.
  • Fixed version: squirrelmail (Debian:3.1) 2:1.4.4-10; squirrelmail (Red Hat:enterprise_linux:3::as) 0:1.4.8-4.el3; squirrelmail (Red Hat:enterprise_linux:4::as) 0:1.4.8-4.el4.

Low priority for now. Upgrade to squirrelmail (Debian:3.1) 2:1.4.4-10; squirrelmail (Red Hat:enterprise_linux:3::as) 0:1.4.8-4.el3; squirrelmail (Red Hat:enterprise_linux:4::as) 0:1.4.8-4.el4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Multiple cross-site scripting (XSS) vulnerabilities in SquirrelMail 1.4.0 through 1.4.9 allow remote attackers to inject arbitrary web script or HTML via the (1) mailto parameter in (a) webmail.php, the (2) session and (3) delete_draft parameters in (b) compose.php, and (4) unspecified vectors involving "a shortcoming in the magicHTML filter."

MediumCVSS 6.8 · v2.0—No exploit Fix available
Published
Dec 5, 2006
Updated
Jun 16, 2026
EPSS
2.3% · 83th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.3%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2006-6142

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
squirrelmailsquirrelmail

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • squirrelmail squirrelmail1.4
  • squirrelmail squirrelmail1.4_rc1
  • squirrelmail squirrelmail1.4.1
  • squirrelmail squirrelmail1.4.2
  • squirrelmail squirrelmail1.4.3
  • squirrelmail squirrelmail1.4.3_r3
  • squirrelmail squirrelmail1.4.3_rc1
  • squirrelmail squirrelmail1.4.3aa
  • squirrelmail squirrelmail1.4.4
  • squirrelmail squirrelmail1.4.4_rc1
  • squirrelmail squirrelmail1.4.5
  • squirrelmail squirrelmail1.4.6
  • squirrelmail squirrelmail1.4.6_cvs
  • squirrelmail squirrelmail1.4.6_rc1
  • squirrelmail squirrelmail1.4.7

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:3.1squirrelmailbefore 2:1.4.4-102:1.4.4-10
Red Hat:enterprise_linux:3::assquirrelmailbefore 0:1.4.8-4.el30:1.4.8-4.el3
Red Hat:enterprise_linux:4::assquirrelmailbefore 0:1.4.8-4.el40:1.4.8-4.el4

Other highest-scoring records for the same primary product.

  • CVE-2017-7692SquirrelMail 1.4.22 (and other versions before 20170427_0200-SVN) allows post-authentication remote code execution via a sendmail.cf file th
    45Plan
  • CVE-2006-2842PHP remote file inclusion vulnerability in functions/plugin.php in SquirrelMail 1.4.6 and earlier, if register_globals is enabled and magic_
    44Plan
  • CVE-2002-0516SquirrelMail 1.2.5 and earlier allows authenticated SquirrelMail users to execute arbitrary commands by modifying the THEME variable in a co
    43Plan

Published before and after this one in the same product

  • ← EarlierCVE-2006-3665Jul 18, 2006 · SquirrelMail 1.4.6 and earlier, with register_globals enabled, allows remote attackers to hijack cookies in src/redirect.php via unknown vec
    17Monitor
  • ← EarlierCVE-2006-4019Aug 11, 2006 · Dynamic variable evaluation vulnerability in compose.php in SquirrelMail 1.4.0 to 1.4.7 allows remote attackers to overwrite arbitrary progr
    28Monitor
  • Later →CVE-2007-1262May 11, 2007 · Multiple cross-site scripting (XSS) vulnerabilities in the HTML filter in SquirrelMail 1.4.0 through 1.4.9a allow remote attackers to inject
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:squirrelmail2:1.4.4-10 · Debian:3.1Package registry (OSV)
red hat:squirrelmail0:1.4.8-4.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    P · data or configuration can be modified
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    P
    Availability impact
    P

    Weakness class (CWE)

    —

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:P/A:P

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    MITRE has no CAPEC/ATT&CK mapping for this CWE.

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records