dbcve.org
InjectionWeakness · CWE-74

CVE-2025-2030

HIGH · 7.3 CVSS v3.1 Published 2025-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A vulnerability was found in Seeyon Zhiyuan Interconnect FE Collaborative Office Platform up to 20250224. It has been rated as critical. Affected by this issue is some unknown functionality of the file /security/addUser.jsp. The manipulation of the argument groupId leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

SQL injection vulnerability in Seeyon Zhiyuan Interconnect FE Collaborative Office Platform's /security/addUser.jsp file allows remote attackers to inject malicious SQL queries via the groupId parameter. The vulnerability is exploitable remotely and a public exploit exists, making immediate remediation critical. This is a high-severity issue due to potential data exfiltration, privilege escalation, or complete database compromise.

MitigationImplement parameterized queries or prepared statements to sanitize the groupId parameter input; deploy a WAF with SQL injection rules as a compensating control; restrict network access to the affected endpoint until the code fix is applied.

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

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
Low
Integrity
Low
Availability
Low

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

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. Confirm Seeyon Zhiyuan Interconnect FE installation
    Identify the installed version of Seeyon Zhiyuan Interconnect FE Collaborative Office Platform through the admin panel, application banner, or version information files in the web root directory
    Affected if The installed version matches or falls within the known affected version range for CVE-2025-2030 (compare your version against the vendor's security advisory)
  2. Verify vulnerable endpoint exists
    Check for the presence of the file /security/addUser.jsp in the web application's document root or accessible paths
    Affected if The file /security/addUser.jsp exists on the server and is accessible via HTTP/HTTPS requests
  3. Test groupId parameter exposure
    Send a request to /security/addUser.jsp with a test value in the groupId parameter (e.g., groupId=1) and observe the application's response
    Affected if The endpoint accepts the groupId parameter and returns a response indicating the parameter is processed without error or sanitization
  4. Check network accessibility of vulnerable endpoint
    Determine if the /security/addUser.jsp endpoint is reachable from untrusted networks or the internet without proper authentication or network segmentation
    Affected if The endpoint is exposed to untrusted network access without authentication or IP restrictions
  5. Review application logs for exploitation indicators
    Examine web server and application logs for SQL injection attempts targeting the groupId parameter in /security/addUser.jsp
    Affected if Log entries show suspicious SQL syntax or unexpected queries involving the groupId parameter

Your environment is affected if you are running a version of Seeyon Zhiyuan Interconnect FE Collaborative Office Platform within the affected range AND the /security/addUser.jsp endpoint with the groupId parameter is accessible and processes input without parameterized query handling.

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

Implement parameterized queries or prepared statements to sanitize the groupId parameter input; deploy a WAF with SQL injection rules as a compensating control; restrict network access to the affected endpoint until the code fix is applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2030 — 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-2030 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