dbcve.org
OpensisApplication · Os4ed

CVE-2025-22930

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-03
Fix available
A fix is available. Upgrade to after 9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
OS4ED openSIS v7.0 to v9.1 was discovered to contain a SQL injection vulnerability via the groupid parameter at /messaging/Group.php.

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

OS4ED openSIS versions 7.0 through 9.1 contain a SQL injection vulnerability in the groupid parameter of /messaging/Group.php, allowing remote attackers to inject arbitrary SQL commands via unsanitized user input.

MitigationApply vendor patch or upgrade to a patched version; implement parameterized queries/prepared statements for the groupid parameter in Group.php.

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
OpensisApplication
Affected:>= 7.0, <= 9.1

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 openSIS installation version
    Check the version.php file in the web root, the admin dashboard footer, or the /assets/version.txt file for the installed version number
    Affected if The version number is >= 7.0 and <= 9.1, indicating the installation falls within the vulnerable range
  2. Locate the vulnerable script
    Navigate to the web root directory and verify the presence of /messaging/Group.php file
    Affected if The file /messaging/Group.php exists in the installation, confirming the vulnerable component is present
  3. Verify groupid parameter usage
    Open Group.php and locate the code handling the groupid parameter, typically in a database query context such as SELECT or WHERE clause
    Affected if The groupid parameter is used in a SQL query without proper sanitization or use of prepared statements
  4. Confirm application accessibility
    Attempt to access the /messaging/Group.php endpoint via HTTP/HTTPS from a browser or curl request
    Affected if The endpoint is accessible remotely and accepts user input through the groupid parameter without additional security controls

A system is affected if openSIS version is between 7.0 and 9.1 inclusive, the /messaging/Group.php file exists, and the groupid parameter is handled in SQL queries without parameterized statements.

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
Upgrade available Upgrade to a release after 9.1
Interim mitigation

Apply vendor patch or upgrade to a patched version; implement parameterized queries/prepared statements for the groupid parameter in Group.php.

Fix this in Opensis Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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