| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Saxum Picker 3.2.10 on Joomla and classified as critical. This affects an unknown part. The manipulation of the argument publicid as part of Parameter results in sql injection. This vulnerability is cataloged as CVE-2018-7178. The attack may be launched remotely. Furthermore, there is an exploit available.
Details
A vulnerability classified as critical has been found in Saxum Picker 3.2.10 on Joomla (Joomla Component). Affected is an unknown code. The manipulation of the argument publicid as part of a Parameter leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
SQL Injection exists in the Saxum Picker 3.2.10 component for Joomla! via the publicid parameter.
The bug was discovered 02/17/2018. The weakness was shared 02/17/2018 as EDB-ID 44136 as not defined exploit (Exploit-DB). The advisory is shared for download at exploit-db.com. This vulnerability is traded as CVE-2018-7178 since 02/15/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.
After immediately, there has been an exploit disclosed. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (44136). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
02/15/2018 🔍02/17/2018 🔍
02/17/2018 🔍
02/17/2018 🔍
02/17/2018 🔍
02/17/2018 🔍
02/18/2018 🔍
06/29/2025 🔍
Sources
Advisory: EDB-ID 44136Status: Not defined
CVE: CVE-2018-7178 (🔍)
GCVE (CVE): GCVE-0-2018-7178
GCVE (VulDB): GCVE-100-113544
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/18/2018 11:07Updated: 06/29/2025 09:00
Changes: 02/18/2018 11:07 (65), 06/27/2020 09:30 (1), 06/29/2025 09:00 (16)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.