Jizhicms 2.3.3 get_fields.html sql injection

A vulnerability classified as critical was found in Jizhicms 2.3.3. This vulnerability affects unknown code of the file /index.php/admins/Fields/get_fields.html. The manipulation leads to sql injection. Using CWE to declare the problem leads to CWE-89. The weakness was published 11/24/2022 as 83. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-45278. The attack can only be initiated within the local network. Technical details are available. There is no exploit available. The current price for an exploit might be approx. USD $0-$5k at the moment. The MITRE ATT&CK project declares the attack technique as T1505. It is declared as not defined. As 0-day the estimated underground price was around $0-$5k. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

User

116

Field

exploit_price_0day1
vulnerability_cvss3_meta_tempscore1
vulnerability_cvss3_meta_basescore1
vulnerability_cvss3_vuldb_tempscore1
vulnerability_cvss3_vuldb_basescore1

Commit Conf

90%25
50%14

Approve Conf

90%25
80%14
IDCommitedUserFieldChangeRemarksAcceptedReasonC
1330436111/24/2022VulD...price_0day$0-$5ksee exploit price documentation11/24/2022accepted
90
1330436011/24/2022VulD...cvss3_meta_tempscore5.5see CVSS documentation11/24/2022accepted
90
1330435911/24/2022VulD...cvss3_meta_basescore5.5see CVSS documentation11/24/2022accepted
90
1330435811/24/2022VulD...cvss3_vuldb_tempscore5.5see CVSS documentation11/24/2022accepted
90
1330435711/24/2022VulD...cvss3_vuldb_basescore5.5see CVSS documentation11/24/2022accepted
90
1330435611/24/2022VulD...cvss2_vuldb_tempscore5.2see CVSS documentation11/24/2022accepted
90
1330435511/24/2022VulD...cvss2_vuldb_basescore5.2see CVSS documentation11/24/2022accepted
90
1330435411/24/2022VulD...cvss3_vuldb_rlXderived from historical data11/24/2022accepted
80
1330435311/24/2022VulD...cvss3_vuldb_eXderived from historical data11/24/2022accepted
80
1330435211/24/2022VulD...cvss3_vuldb_uiNderived from historical data11/24/2022accepted
80
1330435111/24/2022VulD...cvss3_vuldb_prLderived from historical data11/24/2022accepted
80
1330435011/24/2022VulD...cvss3_vuldb_avAderived from historical data11/24/2022accepted
80
1330434911/24/2022VulD...cvss2_vuldb_rlNDderived from historical data11/24/2022accepted
80
1330434811/24/2022VulD...cvss2_vuldb_eNDderived from historical data11/24/2022accepted
80
1330434711/24/2022VulD...cvss2_vuldb_auSderived from historical data11/24/2022accepted
80
1330434611/24/2022VulD...cvss2_vuldb_avAderived from historical data11/24/2022accepted
80
1330434511/24/2022VulD...cvss2_vuldb_rcCderived from vuldb v3 vector11/24/2022accepted
80
1330434411/24/2022VulD...cvss2_vuldb_aiPderived from vuldb v3 vector11/24/2022accepted
80
1330434311/24/2022VulD...cvss2_vuldb_iiPderived from vuldb v3 vector11/24/2022accepted
80
1330434211/24/2022VulD...cvss2_vuldb_ciPderived from vuldb v3 vector11/24/2022accepted
80

19 more entries are not shown

Do you want to use VulDB in your project?

Use the official API to access entries easily!