How severe is CVE-2007-3925?

No CVSS score has been assigned to CVE-2007-3925 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2007-3925?

Affected package information for CVE-2007-3925 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2007-3925?

No fixed version has been published for CVE-2007-3925 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2007-3925 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2007-3925, including 2 documented proof-of-concept exploits on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2007-3925?

CVE-2007-3925 has an EPSS (Exploit Prediction Scoring System) score of 90.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2007-3925?

CVE-2007-3925 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2007-3925?

CVE-2007-3925 affects ipswitch imail server; ipswitch ipswitch collaboration suite. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2007-3925 published, and has it been updated?

CVE-2007-3925 was published on July 21, 2007 and was last updated on April 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2007-3925

Multiple buffer overflows in the IMAP service (imapd32.exe) in Ipswitch IMail Server 2006 before 2006.21 allow remote authenticated users to execute arbitrary code via the (1) Search…

Published

Jul 21, 2007

Updated

Apr 23, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

90.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Multiple buffer overflows in the IMAP service (imapd32.exe) in Ipswitch IMail Server 2006 before 2006.21 allow remote authenticated users to execute arbitrary code via the (1) Search or (2) Search Charset command.

Affected Products

2 products · 2 configurations

Application

imail serveripswitch

≤ 2006.2

range

Application

ipswitch collaboration suiteipswitch

≤ 2006.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-4223remotewindows✓ Verified

IPSwitch IMail Server 2006 - SEARCH Remote Stack Overflow

by ZhenHan.Liu · Jul 25, 2007

Exploit-DB Source

EDB-16487remotewindows✓ Verified

Ipswitch IMail Server - IMAP SEARCH Buffer Overflow (Metasploit)

by Metasploit · Jun 15, 2010

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2007-3925 in your stack?

O3 detects CVE-2007-3925 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works