mJob Time up to 15.7.3.32 Admin Panel Handlers Login.aspx exportSqlQuery_Server sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 3.13 |
Summary
A vulnerability identified as critical has been detected in mJob Time up to 15.7.3.32. Affected by this vulnerability is the function exportSqlQuery_Server of the file Login.aspx of the component Admin Panel Handlers. This manipulation causes sql injection.
The identification of this vulnerability is CVE-2026-9209. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as critical was found in mJob Time up to 15.7.3.32. Affected by this vulnerability is the function exportSqlQuery_Server of the file Login.aspx of the component Admin Panel Handlers. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
mJobTime through build 15.7.3.32 contains an unauthenticated SQL execution vulnerability in the Login.aspx admin panel handlers, where the runQueryButton postback and exportSqlQuery_Server PageMethod execute caller-supplied SQL against the backing Sybase SQL Anywhere database using DBA/sysadmin privileges with no server-side authentication enforced beyond a client-side sessionStorage flag. Attackers can submit arbitrary SQL through these exposed endpoints to invoke xp_cmdshell and xp_read_file, achieving pre-authentication remote code execution as LocalSystem via a single HTTP request.
It is possible to read the advisory at sprocketsecurity.com. This vulnerability is known as CVE-2026-9209 since 05/21/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/08/2026). The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
By approaching the search of inurl:Login.aspx it is possible to find vulnerable targets with Google Hacking.
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 EUVD (EUVD-2026-95035). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 15.7.3.0
- 15.7.3.1
- 15.7.3.2
- 15.7.3.3
- 15.7.3.4
- 15.7.3.5
- 15.7.3.6
- 15.7.3.7
- 15.7.3.8
- 15.7.3.9
- 15.7.3.10
- 15.7.3.11
- 15.7.3.12
- 15.7.3.13
- 15.7.3.14
- 15.7.3.15
- 15.7.3.16
- 15.7.3.17
- 15.7.3.18
- 15.7.3.19
- 15.7.3.20
- 15.7.3.21
- 15.7.3.22
- 15.7.3.23
- 15.7.3.24
- 15.7.3.25
- 15.7.3.26
- 15.7.3.27
- 15.7.3.28
- 15.7.3.29
- 15.7.3.30
- 15.7.3.31
- 15.7.3.32
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: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (VulnCheck): 🔒
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
Google Hack: 🔒
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/21/2026 CVE reserved10/08/2026 Advisory disclosed
10/08/2026 VulDB entry created
10/08/2026 VulDB entry last update
Sources
Advisory: sprocketsecurity.comStatus: Not defined
CVE: CVE-2026-9209 (🔒)
GCVE (CVE): GCVE-0-2026-9209
GCVE (VulDB): GCVE-100-415459
EUVD: 🔒
Entry
Created: 10/08/2026 17:28Updated: 10/08/2026 19:02
Changes: 10/08/2026 17:28 (75), 10/08/2026 19:02 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.