CVE-2011-2753: Multiple cross-site request forgery (CSRF) vulnerabilities in SquirrelMail 1.4.21 and earlier allow remote attackers to hijack the…
Noroxi assessment
Priority: Monitor (action score 27/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: 1% (FIRST EPSS); higher than 65.7% of all records.
- Fixed version: squirrelmail (Debian:5.0) 2:1.4.15-4+lenny5; squirrelmail (Debian:6.0) 2:1.4.21-2; squirrelmail (Red Hat:enterprise_linux:4::as) 0:1.4.8-18.el4.
Low priority for now. Upgrade to squirrelmail (Debian:5.0) 2:1.4.15-4+lenny5; squirrelmail (Debian:6.0) 2:1.4.21-2; squirrelmail (Red Hat:enterprise_linux:4::as) 0:1.4.8-18.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 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.
- Published
- Jul 17, 2011
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-352
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| squirrelmail | squirrelmail | cpe:2.3:a:squirrelmail:squirrelmail |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- squirrelmail squirrelmailup to 1.4.21 inclusive
- squirrelmail squirrelmail0.1
- squirrelmail squirrelmail0.1.1
- squirrelmail squirrelmail0.1.2
- squirrelmail squirrelmail0.2
- squirrelmail squirrelmail0.2.1
- squirrelmail squirrelmail0.3
- squirrelmail squirrelmail0.3.1
+12 more rows
- squirrelmail squirrelmail0.3pre1
- squirrelmail squirrelmail0.3pre2
- squirrelmail squirrelmail0.4
- squirrelmail squirrelmail0.4pre1
- squirrelmail squirrelmail0.4pre2
- squirrelmail squirrelmail0.5
- squirrelmail squirrelmail0.5pre1
- squirrelmail squirrelmail0.5pre2
- squirrelmail squirrelmail1.0
- squirrelmail squirrelmail1.0.1
- squirrelmail squirrelmail1.0.2
- squirrelmail squirrelmail1.0.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:5.0 | squirrelmail | before 2:1.4.15-4+lenny5 | 2:1.4.15-4+lenny5 |
| Debian:6.0 | squirrelmail | before 2:1.4.21-2 | 2:1.4.21-2 |
| Red Hat:enterprise_linux:4::as | squirrelmail | before 0:1.4.8-18.el4 | 0:1.4.8-18.el4 |
| Red Hat:enterprise_linux:5::client_workstation | squirrelmail | before 0:1.4.8-5.el5_7.13 | 0:1.4.8-5.el5_7.13 |
Same product
squirrelmail: all recordsOther 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…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…44Plan
- CVE-2002-0516SquirrelMail 1.2.5 and earlier allows authenticated SquirrelMail users to execute arbitrary commands by modifying the THEME variable in a…43Plan
Published before and after this one in the same product
- ← EarlierCVE-2011-2023Jul 14, 2011 · Cross-site scripting (XSS) vulnerability in functions/mime.php in SquirrelMail before 1.4.22 allows remote attackers to inject arbitrary…18Monitor
- ← EarlierCVE-2011-2752Jul 17, 2011 · CRLF injection vulnerability in SquirrelMail 1.4.21 and earlier allows remote attackers to modify or add preference values via a \n…24Monitor
- Later →CVE-2012-0323Mar 9, 2012 · Cross-site scripting (XSS) vulnerability in the Autocomplete plugin before 3.0 for SquirrelMail allows remote attackers to inject arbitrary…17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:squirrelmail | 2:1.4.15-4+lenny5 · Debian:5.0 | Package registry (OSV) |
| red hat:squirrelmail | 0:1.4.8-18.el4 · Red Hat:enterprise_linux:4::as | Package 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.