How severe is CVE-2015-1503?

CVE-2015-1503 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-1503?

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

How do I fix CVE-2015-1503?

No fixed version has been published for CVE-2015-1503 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-2015-1503 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2015-1503, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations 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-2015-1503?

CVE-2015-1503 has an EPSS (Exploit Prediction Scoring System) score of 91.2%, 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-2015-1503?

CVE-2015-1503 is classified as Path Traversal (CWE-22). 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-2015-1503?

CVE-2015-1503 affects icewarp mail server. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2015-1503?

A Nuclei detection template exists for CVE-2015-1503, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2015-1503 published, and has it been updated?

CVE-2015-1503 was published on May 8, 2018 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2015-1503: Mail Server Path Traversal (High 7.5)

EPSS Exploitation Probability

via FIRST.org ↗

91.2%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 directory traversal vulnerabilities in IceWarp Mail Server before 11.2 allow remote attackers to read arbitrary files via a (1) .. (dot dot) in the file parameter to a webmail/client/skins/default/css/css.php page or .../. (dot dot dot slash dot) in the (2) script or (3) style parameter to webmail/old/calendar/minimizer/index.php.

Affected Products

1 product · 1 configurations

Application

mail servericewarp

< 11.2.0

range

Frequently Asked Questions

Multiple directory traversal vulnerabilities in IceWarp Mail Server before 11.2 allow remote attackers to read arbitrary files via a (1) .. (dot dot) in the file parameter to a webmail/client/skins/default/css/css.php page or .../. (dot dot dot slash dot) in the (2) script or (3) style parameter to webmail/old/calendar/minimizer/index.php.

O3 Security · Impact-Aware SCA

Is CVE-2015-1503 in your stack?

O3 detects CVE-2015-1503 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