Skip to content

Product

sourcecodester Online Library System vulnerabilities

7 published CVES affecting sourcecodester Online Library System, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
7
Critical
3
High
2
Medium
2
Low
0
Unscored
0
CISA KEV
0

Latest sourcecodester Online Library System CVEs

Newest publication first

  1. MediumCVSS 5.4 EPSS 0.55%

    A vulnerability was found in SourceCodester Online Library System 1.0. It has been declared as problematic. This vulnerability affects unknown code of the file admin/books/index.php. The manipulation of the argument id leads to cross site scripting. The attack can be initiated re...

  2. CriticalCVSS 9.8 EPSS 0.85%

    A vulnerability was found in SourceCodester Online Library System 1.0. It has been classified as critical. This affects an unknown part of the file admin/borrowed/index.php. The manipulation of the argument BookPublisher/BookTitle leads to sql injection. It is possible to initiat...

  3. HighCVSS 8.8 EPSS 0.83%

    A vulnerability was found in SourceCodester Online Library System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file admin/books/controller.php. The manipulation of the argument IBSN leads to sql injection. The attack may be launched...

  4. CriticalCVSS 9.8 EPSS 0.94%

    A vulnerability, which was classified as critical, was found in SourceCodester Online Library System 1.0. Affected is an unknown function of the file admin/books/index.php. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely. T...

  5. CriticalCVSS 9.8 EPSS 0.96%

    A vulnerability, which was classified as critical, has been found in SourceCodester Online Library System 1.0. This issue affects some unknown processing of the file admin/login.php. The manipulation of the argument user_email leads to sql injection. The attack may be initiated r...

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.