CVE-2025-22924
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 · uneditedOS4ED openSIS v7.0 through v9.1 contains a SQL injection vulnerability via the stu_id parameter at /modules/students/Student.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 confidenceSQL injection vulnerability in OS4ED openSIS v7.0-v9.1 allows remote attackers to inject malicious SQL queries through the stu_id parameter at /modules/students/Student.php. The lack of parameterized queries or input sanitization on this parameter enables attackers to manipulate database queries, potentially exposing sensitive student data or compromising the entire database.
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>= 7.0, <= 9.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed openSIS versionCheck the application version by accessing the admin dashboard or looking for version files in the installation directory. Compare against the affected range of 7.0 through 9.1.Affected if The installed version is 7.0, 7.x, 8.x, 9.0, or 9.1 (any version >= 7.0 and <= 9.1)
-
Locate vulnerable Student.php fileVerify the presence of /modules/students/Student.php in the web root. This file handles student records and contains the stu_id parameter handling.Affected if The file /modules/students/Student.php exists in the installation
-
Confirm students module is accessibleCheck if the students module is enabled and accessible via the web interface at /modules/students/ or by verifying module configuration.Affected if The students module is enabled and accessible to users
-
Inspect stu_id parameter handlingExamine the Student.php file source code for direct SQL query construction using the stu_id parameter without parameterized queries or prepared statements.Affected if The code uses stu_id in SQL queries without proper parameterization (e.g., direct string concatenation or unsanitized variable insertion)
-
Verify database user privilegesCheck the database user configuration used by openSIS. If the application uses a database account with elevated privileges, the impact of SQL injection is higher.Affected if The database user has more than minimal required privileges (e.g., DDL permissions beyond SELECT/INSERT/UPDATE/DELETE)
A user is affected if running openSIS version 7.0 through 9.1 with the students module enabled and the Student.php file contains direct SQL usage with the stu_id parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries to sanitize the stu_id parameter and all user inputs in Student.php. Apply input validation and upgrade to a patched version if available.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22924 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22924 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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