CVE-2025-4898
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 · uneditedA vulnerability was found in SourceCodester Student Result Management System 1.0. It has been declared as critical. This vulnerability affects the function unlink of the file update_system.php of the component Logo File Handler. The manipulation of the argument old_logo leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
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 confidencePath traversal vulnerability in SourceCodester Student Result Management System 1.0's update_system.php where the old_logo parameter passed to the unlink() function is not properly validated, allowing remote attackers to delete arbitrary files on the server by manipulating the argument with directory traversal sequences (e.g., ../../).
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= 1.0CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm product and versionLocate the application files and check version metadata, typically in a README, version.php, or installer file within the web root directory.Affected if The installed application is Munyweki Student Result Management System version 1.0.
-
Locate vulnerable scriptSearch for the file update_system.php in the web application directory structure, commonly found in admin or includes folders.Affected if The file update_system.php exists in the application installation.
-
Verify web exposureDetermine if the application is accessible over HTTP/HTTPS by accessing the main URL or checking web server configuration.Affected if The application is accessible via web browser or API endpoint.
-
Inspect server access logsReview web server access logs (Apache access.log, Nginx access.log) for POST requests to update_system.php containing '../' patterns in the old_logo parameter.Affected if Log entries show requests to update_system.php with directory traversal sequences like ../../ in the old_logo parameter.
-
Check for unauthorized file deletionCompare current file list in the web root and adjacent directories against known-good backups or deployment records.Affected if Files exist that were not intentionally deleted or files are missing from directories where they should be present.
If the environment runs Munyweki Student Result Management System 1.0 with web-accessible update_system.php, it is vulnerable to arbitrary file deletion via directory traversal in the old_logo 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 strict input validation on the old_logo parameter using allowlist validation or normalizing and verifying the resolved path stays within an expected directory before passing to unlink(). Sanitize path traversal sequences and ensure the file being deleted exists within the intended upload directory.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4898 — 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-4898 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