dbcve.org
RuisibiApplication · Ruisitech

CVE-2025-57140

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
rsbi-pom 4.7 is vulnerable to SQL Injection in the /bi/service/model/DatasetService path.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

rsbi-pom version 4.7 contains a SQL Injection vulnerability in the /bi/service/model/DatasetService REST endpoint. An unauthenticated remote attacker can exploit this by sending malicious SQL payloads through the dataset service parameters, potentially allowing complete database compromise, data exfiltration, or operating system command execution via database features.

MitigationImmediately restrict network access to the DatasetService endpoint, implement web application firewall rules to detect and block SQL injection patterns, and refactor the vulnerable code to use parameterized queries/prepared statements instead of dynamic SQL construction. If a patched version exists, upgrade promptly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RuisibiApplication
Affected:= 4.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed rsbi-pom version
    Locate and examine the rsbi-pom version. Check the application's manifest file, version descriptor, or about page. Common paths include WEB-INF/lib目录下包含rsbi-pom的jar文件内的版本信息，或应用程序自带版本查询接口。
    Affected if 版本为 4.7
  2. Verify DatasetService endpoint is accessible
    确认服务器上 /bi/service/model/DatasetService 端点是否已部署并可访问。检查应用的URL路由配置或尝试访问该路径观察响应。
    Affected if 端点可访问且返回应用响应而非404错误
  3. Check if endpoint accepts parameters
    检查DatasetService是否处理用户传入的参数。可通过查看应用日志、网络请求或使用测试工具向该端点发送包含参数的请求来验证。
    Affected if 端点接受并处理参数传入

当已安装版本为4.7且/bi/service/model/DatasetService端点可访问并处理用户输入时，当前环境存在该SQL注入漏洞风险。

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict network access to the DatasetService endpoint, implement web application firewall rules to detect and block SQL injection patterns, and refactor the vulnerable code to use parameterized queries/prepared statements instead of dynamic SQL construction. If a patched version exists, upgrade promptly.

Fix this in Ruisibi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57140 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data