Skip to content
Fencer Intel
medium 6.8

CVE-2011-2753 json

Multiple cross-site request forgery (CSRF) vulnerabilities in SquirrelMail 1.4.21 and earlier allow remote attackers to hijack the authenti…

published 2011-07-17 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2728

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

Multiple cross-site request forgery (CSRF) vulnerabilities in SquirrelMail 1.4.21 and earlier allow remote attackers to hijack the authentication of unspecified victims via vectors involving (1) the empty trash implementation and (2) the Index Order (aka options_order) page, a different issue than CVE-2010-4555.

Patch / fix

  • squirrelmail RHEL 4 1.4.8-18.el4
  • squirrelmail RHEL 5 1.4.8-5.el5_7.13

red hat advisories RHSA-2012:0103

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-2011-2753 updated cvss 4.3

SquirrelMail: CSRF in the empty trash feature and in Index Order page

  • Red Hat Enterprise Linux (v. 5 server) squirrelmail 1.4.8-5.el5_7.13 Red Hat Enterprise Linux AS version 4 squirrelmail 1.4.8-18.el4 Red Hat Enterprise Linux Desktop version 4 squirrelmail 1.4.8-18.el4 Red Hat Enterprise Linux ES version 4 squirrelmail 1.4.8-18.el4 Red Hat Enterprise Linux WS version 4 squirrelmail 1.4.8-18.el4 Red Hat RHEL Desktop Workstation (v. 5 client) squirrelmail 1.4.8-5.el5_7.13
    fixed: vendor fix RHSA-2012:0103

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

1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

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-352 Cross-Site Request Forgery

References

Sources

Fencer Intel 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.