CVE-2018-6583: SQL Injection exists in the Timetable Responsive Schedule 1.5 component for Joomla! via a view=event&alias= re
CVE-2018-6583 is a critical-severity flaw (CVSS 9.8) affecting timetable responsive schedule. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
SQL Injection exists in the Timetable Responsive Schedule 1.5 component for Joomla! via a view=event&alias= request.
Why this priority
- Critical severity
- EPSS top 3%: very likely to be exploited
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 19.1% (top 3%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2018-02-17 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-6583?
timetable responsive schedule: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2018-6583 being exploited?
CVE-2018-6583 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-6583 affect?
CVE-2018-6583 affects timetable responsive schedule. Severity is critical (CVSS 9.8). SQL Injection exists in the Timetable Responsive Schedule 1.5 component for Joomla! via a view=event&alias= request.
How urgent is CVE-2018-6583?
Priority 69/100. Critical severity; EPSS top 3%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action