CVE-2025-22923
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 · uneditedAn issue in OS4ED openSIS v8.0 through v9.1 allows attackers to execute a directory traversal and delete files by sending a crafted POST request to /Modules.php?modname=users/Staff.php&removefile.
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 confidenceOS4ED openSIS versions 8.0 through 9.1 contain a path traversal vulnerability in the Staff.php module. Attackers can craft POST requests to /Modules.php?modname=users/Staff.php&removefile with directory traversal sequences (e.g., ../../) in the removefile parameter to navigate outside the intended directory and delete arbitrary files on the server.
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>= 8.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 openSIS versionLocate the version file or check the admin dashboard footer for the installed openSIS version number. Common paths include /version.php, /config.php, or the administration interface.Affected if The installed version falls within 8.0 through 9.1 inclusive.
-
Confirm Staff.php module presenceVerify that the file /modules/users/Staff.php exists in the web root directory.Affected if The Staff.php module file exists in the users directory.
-
Check Modules.php routing to affected endpointInspect the web server access logs or application routing configuration for requests to /Modules.php with modname=users/Staff.phpAffected if The application routes requests to the Staff.php module through Modules.php.
-
Verify removefile parameter handlingSearch the Staff.php source code for the removefile parameter handling logic. Look for file deletion operations using this parameter.Affected if The code processes the removefile parameter without proper sanitization.
-
Inspect input validation on file parametersReview the Staff.php file for validation functions that sanitize or restrict the removefile parameter value, particularly checking for directory traversal sequence filtering.Affected if No input validation exists, or validation does not block ../ sequences in the removefile parameter.
The environment is affected if openSIS versions 8.0-9.1 are running, the Staff.php module is accessible, and the removefile parameter lacks proper directory traversal validation.
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 strict input validation on the removefile parameter using whitelist-based file path verification, normalize and resolve paths before file operations, and ensure the application runs with minimal file system permissions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22923 — 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-22923 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