CVE-2022-36719: SQL Injection
First published: Thu Aug 25 2022(Updated: )
Library Management System v1.0 was discovered to contain a SQL injection vulnerability via the ok parameter at /admin/history.php.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Library Management System | =1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-36719?
CVE-2022-36719 is classified as a high severity SQL injection vulnerability.
How do I fix CVE-2022-36719?
To fix CVE-2022-36719, validate and sanitize user inputs, especially the ok parameter in the affected URL.
What platforms are affected by CVE-2022-36719?
CVE-2022-36719 affects Library Management System version 1.0.
What type of vulnerability is CVE-2022-36719?
CVE-2022-36719 is a SQL injection vulnerability that can allow an attacker to manipulate database queries.
Can CVE-2022-36719 lead to data breaches?
Yes, CVE-2022-36719 can lead to data breaches by allowing attackers to access sensitive data in the database.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/author
- agent/last-modified-date
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/library management system project
- canonical/library management system
- version/library management system/1.0