CVE-2005-2095: options_identities.php in SquirrelMail 1.4.4 and earlier uses the extract function to process the $_POST variable, which allows remote…
Noroxi assessment
Priority: Monitor (action score 18/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 91.1% of all records.
- Fixed version: squirrelmail (Debian:3.0) 1:1.2.6-4; squirrelmail (Debian:3.1) 2:1.4.4-6sarge1; squirrelmail (Red Hat:enterprise_linux:3::as) 0:1.4.3a-11.EL3.
Low priority for now. Upgrade to squirrelmail (Debian:3.0) 1:1.2.6-4; squirrelmail (Debian:3.1) 2:1.4.4-6sarge1; squirrelmail (Red Hat:enterprise_linux:3::as) 0:1.4.3a-11.EL3 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
options_identities.php in SquirrelMail 1.4.4 and earlier uses the extract function to process the $_POST variable, which allows remote attackers to modify or read the preferences of other users, conduct cross-site scripting XSS) attacks, and write arbitrary files.
- Published
- Jul 13, 2005
- Updated
- Jun 16, 2026
- EPSS
- 4.2% · 91th percentile
- CWE
- —
Report tools
Action score
18
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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 squirrelmail1.0.4
- squirrelmail squirrelmail1.0.5
- squirrelmail squirrelmail1.2.0
- squirrelmail squirrelmail1.2.1
- squirrelmail squirrelmail1.2.10
- squirrelmail squirrelmail1.2.11
- squirrelmail squirrelmail1.2.2
- squirrelmail squirrelmail1.2.3
+12 more rows
- squirrelmail squirrelmail1.2.4
- squirrelmail squirrelmail1.2.5
- squirrelmail squirrelmail1.2.6
- squirrelmail squirrelmail1.2.7
- squirrelmail squirrelmail1.2.8
- squirrelmail squirrelmail1.2.9
- squirrelmail squirrelmail1.4
- squirrelmail squirrelmail1.4.0
- squirrelmail squirrelmail1.4.1
- squirrelmail squirrelmail1.4.2
- squirrelmail squirrelmail1.4.3
- squirrelmail squirrelmail1.4.3_rc1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:3.0 | squirrelmail | before 1:1.2.6-4 | 1:1.2.6-4 |
| Debian:3.1 | squirrelmail | before 2:1.4.4-6sarge1 | 2:1.4.4-6sarge1 |
| Red Hat:enterprise_linux:3::as | squirrelmail | before 0:1.4.3a-11.EL3 | 0:1.4.3a-11.EL3 |
| Red Hat:enterprise_linux:4::as | squirrelmail | before 0:1.4.3a-12.EL4 | 0:1.4.3a-12.EL4 |
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-2004-1036Mar 1, 2005 · Cross-site scripting (XSS) vulnerability in the decoding of encoded text in certain headers in mime.php for SquirrelMail 1.4.3a and…28Monitor
- ← EarlierCVE-2005-1769Jun 16, 2005 · Multiple cross-site scripting (XSS) vulnerabilities in SquirrelMail 1.4.0 through 1.4.4 allow remote attackers to inject arbitrary web…18Monitor
- Later →CVE-2006-0188Feb 23, 2006 · webmail.php in SquirrelMail 1.4.0 to 1.4.5 allows remote attackers to inject arbitrary web pages into the right frame via a URL in the…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 / package | Fixed version | Source |
|---|---|---|
| debian:squirrelmail | 1:1.2.6-4 · Debian:3.0 | Package registry (OSV) |
| red hat:squirrelmail | 0:1.4.3a-11.EL3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2015-07-14 |
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.
- Published
- First PoC+3653 d
- TodayNov 16, 2026+7796 d
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
- none
- Availability
- none
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
AV:N/AC:M/Au:N/C:P/I:N/A:N
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
Show all references (12 more)Show less
- lists.apple.com/archives/security-announce/2005/Aug/msg00000.html
- www.debian.org/security/2005/dsa-756
- www.gulftech.org/?node=research&article_id=00090-07142005
- www.novell.com/linux/security/advisories/2005_18_sr.html
- www.redhat.com/support/errata/RHSA-2005-595.html
- www.securityfocus.com/archive/1/405200
- www.securityfocus.com/archive/1/405202
- www.securityfocus.com/bid/14254
- www.squirrelmail.org/security/issue/2005-07-13
- bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163047
- exchange.xforce.ibmcloud.com/vulnerabilities/21359
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10500
Vendor advisories and official records. Exploit/PoC links are deliberately left out.