Skip to content

Vendor

rosariosis vulnerabilities

23 published CVES affecting rosariosis, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
23
Critical
4
High
3
Medium
16
Low
0
Unscored
0
CISA KEV
0
Atom feed of rosariosis alerts

Products

Latest rosariosis CVEs

Newest publication first

  1. MediumCVSS 5.3 EPSS 0.24%

    A vulnerability was found in francoisjacquet RosarioSIS up to 12.8. This issue affects some unknown processing of the file Modules.php. Performing a manipulation results in cross-site request forgery. Remote exploitation of the attack is possible. Upgrading to version 12.9 is cap...

  2. MediumCVSS 5.3 EPSS 0.46%

    A flaw has been found in francoisjacquet RosarioSIS up to 12.8. This affects the function DBUpdate of the file Discipline/Referrals.php. This manipulation causes authorization bypass. The attack may be initiated remotely. The exploit has been published and may be used. Upgrading...

  3. MediumCVSS 5.4 EPSS 0.73%

    A Cross Site Scripting (XSS) vulnerability exists in RosarioSIS before 7.6.1 via the xss_clean function in classes/Security.php, which allows remote malicious users to inject arbitrary JavaScript or HTML. An example of affected components are all Markdown input fields.

  4. MediumCVSS 6.1 EPSS 2.3% PoC

    Reflected Cross-site scripting (XSS) vulnerability in RosarioSIS 8.2.1 allows attackers to inject arbitrary HTML via the search_term parameter in the modules/Scheduling/Courses.php script.

  5. CriticalCVSS 9.8 EPSS 50.6% Scanner template

    An unauthenticated SQL Injection vulnerability in Rosario Student Information System (aka rosariosis) before 8.1.1 allows remote attackers to execute PostgreSQL statements (e.g., SELECT, INSERT, UPDATE, and DELETE) through /Side.php via the syear parameter.

  6. MediumCVSS 6.1 EPSS 6.3% Public exploit Scanner template

    RosarioSIS 6.7.2 is vulnerable to XSS, caused by improper validation of user-supplied input by the PrintSchedules.php script. A remote attacker could exploit this vulnerability using the include_inactive parameter in a crafted URL.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.