GWE Systems JEvents Component up to 3.6.87 on Joomla sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GWE Systems JEvents Component up to 3.6.87 on Joomla. It has been classified as critical. The impacted element is an unknown function. Performing a manipulation results in sql injection. This vulnerability is cataloged as CVE-2025-49467. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in GWE Systems JEvents Component up to 3.6.87 on Joomla. This affects an unknown code block. The manipulation with an unknown input 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. The summary by CVE is:
A SQL injection vulnerability in JEvents component before 3.6.88 and 3.6.82.1 for Joomla was discovered. The extension is vulnerable to SQL injection via publicly accessible actions to list events by date ranges.
The weakness was shared by José Apari Pantigozo. This vulnerability is uniquely identified as CVE-2025-49467 since 06/05/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 3.6.82.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-18196). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 3.6.0
- 3.6.1
- 3.6.2
- 3.6.3
- 3.6.4
- 3.6.5
- 3.6.6
- 3.6.7
- 3.6.8
- 3.6.9
- 3.6.10
- 3.6.11
- 3.6.12
- 3.6.13
- 3.6.14
- 3.6.15
- 3.6.16
- 3.6.17
- 3.6.18
- 3.6.19
- 3.6.20
- 3.6.21
- 3.6.22
- 3.6.23
- 3.6.24
- 3.6.25
- 3.6.26
- 3.6.27
- 3.6.28
- 3.6.29
- 3.6.30
- 3.6.31
- 3.6.32
- 3.6.33
- 3.6.34
- 3.6.35
- 3.6.36
- 3.6.37
- 3.6.38
- 3.6.39
- 3.6.40
- 3.6.41
- 3.6.42
- 3.6.43
- 3.6.44
- 3.6.45
- 3.6.46
- 3.6.47
- 3.6.48
- 3.6.49
- 3.6.50
- 3.6.51
- 3.6.52
- 3.6.53
- 3.6.54
- 3.6.55
- 3.6.56
- 3.6.57
- 3.6.58
- 3.6.59
- 3.6.60
- 3.6.61
- 3.6.62
- 3.6.63
- 3.6.64
- 3.6.65
- 3.6.66
- 3.6.67
- 3.6.68
- 3.6.69
- 3.6.70
- 3.6.71
- 3.6.72
- 3.6.73
- 3.6.74
- 3.6.75
- 3.6.76
- 3.6.77
- 3.6.78
- 3.6.79
- 3.6.80
- 3.6.81
- 3.6.82
- 3.6.83
- 3.6.84
- 3.6.85
- 3.6.86
- 3.6.87
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: JEvents Component 3.6.82.1
Timeline
06/05/2025 🔍06/12/2025 🔍
06/12/2025 🔍
06/16/2025 🔍
Sources
Researcher: José Apari PantigozoStatus: Confirmed
CVE: CVE-2025-49467 (🔍)
GCVE (CVE): GCVE-0-2025-49467
GCVE (VulDB): GCVE-100-312429
EUVD: 🔍
Entry
Created: 06/12/2025 18:18Updated: 06/16/2025 15:25
Changes: 06/12/2025 18:18 (70), 06/13/2025 01:10 (1), 06/16/2025 15:25 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.