aiyiyi121 SxDevOps 1.0/1.1 Settings settings.py hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 1.50- |
Summary
A vulnerability marked as critical has been reported in aiyiyi121 SxDevOps 1.0/1.1. Impacted is an unknown function of the file backend/sxdevops/settings.py of the component Settings Handler. This manipulation causes hard-coded credentials. The identification of this vulnerability is CVE-2026-93970. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to install a patch to address this issue. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.
Details
A vulnerability has been found in aiyiyi121 SxDevOps 1.0/1.1 and classified as critical. Affected by this vulnerability is an unknown code of the file backend/sxdevops/settings.py of the component Settings Handler. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-93970. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.
Applying the patch 2b4bf8585c3e731e7a8af30801ea46680bc783f9 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 2b4bf8585c3e731e7a8af30801ea46680bc783f9
Timeline
09/19/2026 Advisory disclosed09/19/2026 VulDB entry created
09/19/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 16
Status: Confirmed
CVE: CVE-2026-93970 (🔒)
GCVE (CVE): GCVE-0-2026-93970
GCVE (VulDB): GCVE-100-407929
Entry
Created: 09/19/2026 12:20Changes: 09/19/2026 12:20 (57)
Complete: 🔍
Submitter: _lxf
Cache ID: 216::103
Submit
Accepted
- Submit #944385: aiyiyi121 SxDevOps 1.1 Use of Hard-coded Cryptographic Key (by _lxf)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.