CVE-2004-1621 : Detail

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	3.13%	–	–
2022-03-06	–	–	3.13%	–	–
2022-04-03	–	–	3.13%	–	–
2022-05-15	–	–	3.13%	–	–
2022-12-18	–	–	3.13%	–	–
2023-01-01	–	–	3.13%	–	–
2023-02-05	–	–	3.13%	–	–
2023-03-12	–	–	–	0.48%	–
2023-07-02	–	–	–	0.48%	–
2023-11-12	–	–	–	0.65%	–
2024-01-28	–	–	–	0.93%	–
2024-02-11	–	–	–	0.93%	–
2024-03-03	–	–	–	0.93%	–
2024-06-02	–	–	–	0.93%	–
2024-11-17	–	–	–	0.93%	–
2024-12-22	–	–	–	1.85%	–
2025-03-09	–	–	–	2.14%	–
2025-01-19	–	–	–	1.85%	–
2025-03-09	–	–	–	2.14%	–
2025-03-18	–	–	–	–	1.52%
2025-03-30	–	–	–	–	1.91%
2025-03-30	–	–	–	–	1.91,%

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Date	Percentile
2022-02-06	65%
2022-03-06	66%
2022-04-03	82%
2022-05-15	83%
2022-12-18	84%
2023-01-01	83%
2023-02-05	84%
2023-03-12	72%
2023-07-02	73%
2023-11-12	77%
2024-01-28	81%
2024-02-11	82%
2024-03-03	83%
2024-06-02	83%
2024-11-17	84%
2024-12-22	88%
2025-03-09	89%
2025-01-19	88%
2025-03-09	89%
2025-03-18	8%
2025-03-30	82%
2025-03-30	82%

source: https://www.securityfocus.com/bid/11458/info It is reported that Lotus Domino is susceptible to a cross-site scripting and an HTML injection vulnerability. These issues are due to a failure of the application to properly sanitize user-supplied input. The cross-site scripting issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks. The HTML injection issue may allow an attacker to inject malicious HTML and script code into the application. An unsuspecting user viewing a page that contains the malicious comment will have the attacker-supplied script code executed within their browser in the context of the vulnerable site. This issue may be leveraged to steal cookie based authentication credentials. Other attacks are also possible. http://www.example.com/FormReflectingURLValue?OpenForm&Field=%5B%3Cscript%3E%2E%2E%2E%2E%2E%3C%2Fscript%3E%5D