/

CVE-2026-93014

Severity:

HIGH RISK

(7.1)

Path Traversal (CWE-22) in RosarioSIS File Handling

CVE-2026-93014

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Unauthorized File Deletion

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

RosarioSIS does not adequately validate the filename request parameter in its Users and Students modules, allowing authenticated users to reference files outside the intended upload directory. Under affected deployment conditions, this may let an attacker unlink allow-listed resources and other users' documents across the installation.

Affected context

The vulnerability occurs in RosarioSIS file-handling functionality used by the Users and Students modules. It becomes risky when an authenticated user can submit a filename value that is resolved against an upload directory without sufficient canonicalization and boundary validation, potentially allowing references to CSS, XML, JSON, and document files elsewhere in the installation.

Exploit preconditions

  • Attack surface: File unlink or deletion requests in the Users and Students modules
  • Required access: An authenticated RosarioSIS account with access to the affected functionality
  • Trigger point: Processing of the filename request parameter
  • Why exploitation is possible: The application does not reliably constrain the resolved file path to the intended upload directory
  • Required target condition: The target file must be reachable by the application process and removable under its filesystem permissions

Why this happens

The underlying bug is insufficient validation of a user-controlled filename before it is converted into a filesystem path. When directory references are accepted without canonicalizing the resulting path and enforcing an allowed-directory boundary, the requested resource can resolve outside the intended upload location. This behavior maps to CWE-22, Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal.

Potential impact

  • An attacker may delete application CSS, XML, or JSON resources.
  • An attacker could remove documents belonging to other users.
  • The application may experience broken functionality or disrupted operations.
  • Data availability and integrity could be reduced across the installation.
  • Repeated abuse may contribute to denial-of-service conditions.

General mitigation guidance

Mitigation generally focuses on treating filename parameters as untrusted

input and avoiding direct filesystem operations based on user-provided paths.

Common defensive patterns include:

  • Canonicalizing paths before authorization and file operations.
  • Enforcing that resolved paths remain within a designated, trusted directory.
  • Preferencing opaque server-generated file identifiers over client-supplied paths.
  • Allowing only expected filename formats and rejecting path separators or directory references.
  • Separating uploaded content from application resources and other users' files.
  • Applying least-privilege filesystem permissions to the application process.
  • Using authorization checks that bind each file to its owning user or record.
  • Recording and reviewing file deletion events.

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules covering filesystem operations that consume request parameters.
  • Code review checks for missing canonicalization and directory-boundary validation.
  • Tests that verify file operations cannot resolve outside approved storage roots.
  • Web application monitoring for unusual filename values and repeated deletion attempts.
  • Policy enforcement requiring server-side file identifiers and centralized storage helpers.
  • Automated security review tools that flag path construction from untrusted input.

Sources

SourceLink
gist.github.comgist.github.com/kazisabu/68bd095bc05b2341db318a063e05e644
gitlab.comgitlab.com/francoisjacquet/rosariosis
gitlab.comgitlab.com/francoisjacquet/rosariosis/-/commit/701f9c07330157181362927a40d4f8dcc8094d90
vulncheck.comvulncheck.com/advisories/rosariosis-before-12.9-path-traversal-in-file-deletion-via-filename-parameter

Frequently asked

questions

It may be exploitable through the RosarioSIS web application when an attacker

has authenticated access to an affected Users or Students file-handling

function.

An authenticated account capable of reaching the relevant request handler is

generally required. The account's exact permissions and the application's

filesystem permissions influence the scope of possible deletion.

Treat filename parameters as untrusted, use server-side file identifiers, and

verify that every canonicalized path remains within the intended storage

directory before performing an operation.

Centralize file access logic, enforce ownership and least-privilege checks,

separate user uploads from application resources, and test path-boundary

enforcement in code review and automated security testing.

Find out what's already
exploitable in your codebase.