High severity · published Jul 19, 2022
CVE-2022-34024
Barangay Management System v1.0 was discovered to contain an arbitrary file upload vulnerability via the resident module editing function at /bmis/pages/resident/resident.php
7.2
CVSS
1.4%
EPSS
No
On KEV
Description
Barangay Management System v1.0 was discovered to contain an arbitrary file upload vulnerability via the resident module editing function at /bmis/pages/resident/resident.php.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.4% · higher than 73% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
BM
Barangay Management System · Barangay Management System Project
1.0 · source: NVD
Affected product
BM
Barangay Management System
Barangay Management System Project
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-34024
CVE.org
https://www.cve.org/CVERecord?id=CVE-2022-34024
Exploit
https://github.com/sorabug/bug_report/blob/main/vendors/itsourcecode.com/barangay-management-system/RCE-1.md
More from Barangay Management System
9.8
CVE-2022-35175
Barangay Management System v1.0 was discovered to contain a SQL injection vulnerability via the hidden_id parameter at /blotter/blotter.php
9.8
CVE-2022-34023
Barangay Management System v1.0 was discovered to contain a SQL injection vulnerability via the hidden_id parameter at /officials/officials.php
8.8
CVE-2022-34557
Barangay Management System v1.0 was discovered to contain a SQL injection vulnerability via the hidden_id parameter at /pages/permit/permit.php
7.2
CVE-2022-43228
Barangay Management System v1.0 was discovered to contain a SQL injection vulnerability via the hidden_id parameter at /clearance/clearance.php
7.2
CVE-2022-34120
Barangay Management System v1.0 was discovered to contain a remote code execution (RCE) vulnerability via the module editing function at /pages/activity/activity.php