How severe is CVE-2007-2631?

CVE-2007-2631 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2007-2631 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2007-2631?

CVE-2007-2631 affects Squirrelmail. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2007-2631?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2007-2631 published?

CVE-2007-2631 was published on 2007-05-13 and last updated on 2026-06-16.

CVE-2007-2631

CVE-2007-2631 is a high-severity vulnerability in Squirrelmail with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 1% (69th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Squirrelmail
Published: 2007-05-13
Last modified: 2026-06-16

Description

Cross-site request forgery (CSRF) vulnerability in SquirrelMail 1.4.8-4.fc6 and earlier allows remote attackers to perform unspecified actions as arbitrary users via unspecified vectors. NOTE: this issue might overlap CVE-2007-2589 or CVE-2002-1648.

Frequently asked questions

What is CVE-2007-2631?: Cross-site request forgery (CSRF) vulnerability in SquirrelMail 1.4.8-4.fc6 and earlier allows remote attackers to perform unspecified actions as arbitrary users via unspecified vectors. NOTE: this issue might overlap CVE-2007-2589 or CVE-2002-1648.
How severe is CVE-2007-2631?: CVE-2007-2631 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2007-2631 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2007-2631?: CVE-2007-2631 affects Squirrelmail. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2007-2631?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2007-2631 published?: CVE-2007-2631 was published on 2007-05-13 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:squirrelmail:squirrelmail:*:*:*:*:*:*:*:*

More vulnerabilities in Squirrelmail

CVE-2004-0521 — Critical (CVSS 10.0): SQL injection vulnerability in SquirrelMail before 1.4.3 RC1 allows remote attackers to execute unauthorized SQL…
CVE-2002-0516 — Critical (CVSS 10.0): SquirrelMail 1.2.5 and earlier allows authenticated SquirrelMail users to execute arbitrary commands by modifying the…
CVE-2020-14932 — Critical (CVSS 9.8): compose.php in SquirrelMail 1.4.22 calls unserialize for the $mailtodata value, which originates from an HTTP GET…
CVE-2020-14933 — High (CVSS 8.8): compose.php in SquirrelMail 1.4.22 calls unserialize for the $attachments value, which originates from an HTTP POST…
CVE-2018-8741 — High (CVSS 8.8): A directory traversal flaw in SquirrelMail 1.4.22 allows an authenticated attacker to exfiltrate (or potentially…
CVE-2017-7692 — High (CVSS 8.8): SquirrelMail 1.4.22 (and other versions before 20170427_0200-SVN) allows post-authentication remote code execution via…

All CVEs affecting Squirrelmail →