CVE-2018-11324
CVE-2018-11324 is a medium-severity vulnerability in Joomla Joomla! with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: Medium (CVSS 3.x base score 5.9)
- CVSS v2: 4.3
- EPSS exploit prediction: 1% (68th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-362
- Affected product: Joomla Joomla!
- Published:
- Last modified:
Description
An issue was discovered in Joomla! Core before 3.8.8. A long running background process, such as remote checks for core or extension updates, could create a race condition where a session that was expected to be destroyed would be recreated.
Frequently asked questions
- What is CVE-2018-11324?
- An issue was discovered in Joomla! Core before 3.8.8. A long running background process, such as remote checks for core or extension updates, could create a race condition where a session that was expected to be destroyed would be recreated.
- How severe is CVE-2018-11324?
- CVE-2018-11324 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
- Is CVE-2018-11324 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2018-11324?
- CVE-2018-11324 affects Joomla Joomla!. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2018-11324?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2018-11324 published?
- CVE-2018-11324 was published on 2018-05-22 and last updated on 2026-06-17.
References
- http://www.securityfocus.com/bid/104274
- http://www.securitytracker.com/id/1040966
- https://developer.joomla.org/security-centre/735-20180507-core-session-deletion-race-condition.html
Affected products (1)
- cpe:2.3:a:joomla:joomla\!:*:*:*:*:*:*:*:*
More vulnerabilities in Joomla Joomla!
- CVE-2026-48904 — Critical (CVSS 9.8): An improper access check allows privelege escalation through the com_users group editing webservice endpoint.
- CVE-2026-48902 — Critical (CVSS 9.8): The password and username reset features created plain http links for https connections if the "Force SSL" flag wasn't…
- CVE-2026-48899 — Critical (CVSS 9.8): An improper access check allows privilege escalation through the com_users batch task.
- CVE-2026-48898 — Critical (CVSS 9.8): An improper access check allows privilege escalation through the com_users batch task.
- CVE-2026-40383 — Critical (CVSS 9.8): An improper validation of user-supplied input leads to a local file inclusion vulnerability.
- CVE-2026-35223 — Critical (CVSS 9.8): An improper access check allows unauthorized access to com_config webservice endpoints.
All CVEs affecting Joomla Joomla! →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…