Com Scheduling Component
Vendor:
First CVE: Feb 19, 2008 · Active for 18 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
7.5
Avg CVSS
Higher Avg CVSS than 50% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Com Scheduling Component over time
Volume of CVEsAvg CVSS Base Score
First CVE
Feb 19, 2008
18 years ago
Most Recent CVE
Feb 19, 2008
6,730 days ago
CVE Severity & Scoring
Com Scheduling Component1 CVEs
100%
All CVEs352,231 CVEs
45%
40%
11%
High
Attack Vector
Local0 (0.0%)
Network0 (0.0%)
Unknown1 (100.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High0 (0.0%)
Unknown1 (100.0%)
User Interaction
None0 (0.0%)
Unknown1 (100.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None0 (0.0%)
Unknown1 (100.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2008-0810HIGH SQL injection vulnerability in the com_scheduling module for Joomla! and Mambo allows remote attackers to execute arbitrary SQL commands via the id parameter. | Feb 19, 2008 | 7.5 | 32 | NO | YES |
Exploit Exposure
Signals from CVEs in this product scope (1 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
1 CVE
100.0% of CVEs· 93rd percentile
Social Chatter
Signals from CVEs in this product scope (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Com Scheduling Component
Top CWEs
Versions
No cataloged versions.