CVE-2022-27927 in the critical feed json
A SQL injection vulnerability exists in Microfinance Management System 1.0 when MySQL is being used as the application database.
published 2022-04-19 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-32415
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.8%
- EPSS 13.8% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
A SQL injection vulnerability exists in Microfinance Management System 1.0 when MySQL is being used as the application database. An attacker can issue SQL commands to the MySQL database through the vulnerable course_code and/or customer_number parameter.
Exploit prediction
13.83% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Microfinance Management System 1.0 - SQL Injection nuclei detection template
- github.com https://github.com/erengozaydin/Microfinance-Management-System-V1.0-SQL-Injection-Vulnerability-Unauthenticated referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/167017/Microfinance-Management-System-1.0-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/erengozaydin/Microfinance-Management-System-V1.0-SQL-Injection-Vulnerability-Unauthenticated
exploit, third-party-advisory
-
packetstormsecurity.com
/files/167017/Microfinance-Management-System-1.0-SQL-Injection.html
exploit, third-party-advisory, vdb-entry
-
sourcecodester.com
/php/14822/microfinance-management-system.html
product, third-party-advisory
Sources
- CVE List CVE-2022-27927
- NVD CVE-2022-27927
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.