ruisibi rsbi-os 4.7 sqlite-jdbc testDataSource.action code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in ruisibi rsbi-os 4.7. Affected is an unknown function of the file /rsbi/model/testDataSource.action of the component sqlite-jdbc. Performing a manipulation results in Remote Privilege Escalation. This vulnerability is identified as CVE-2025-57141. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical has been found in ruisibi rsbi-os 4.7. This affects some unknown processing of the file /rsbi/model/testDataSource.action of the component sqlite-jdbc. The manipulation with an unknown input leads to a remote privilege escalation vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
rsbi-os 4.7 is vulnerable to Remote Code Execution (RCE) in sqlite-jdbc.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-57141 since 08/17/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. 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 09/08/2025). The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
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: Code injectionCWE: CWE-94 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/17/2025 CVE reserved09/08/2025 Advisory disclosed
09/08/2025 VulDB entry created
09/09/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-57141 (🔒)
GCVE (CVE): GCVE-0-2025-57141
GCVE (VulDB): GCVE-100-323091
Entry
Created: 09/08/2025 17:17Updated: 09/09/2025 04:38
Changes: 09/08/2025 17:17 (53), 09/09/2025 04:38 (2)
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.