Tongda OA 2017 up to 11.9 delete.php PROJ_ID_STR sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Tongda OA 2017 up to 11.9. This affects an unknown function of the file general/project/proj/delete.php. This manipulation of the argument PROJ_ID_STR causes sql injection. This vulnerability is tracked as CVE-2023-7180. Moreover, an exploit is present. It is recommended to upgrade the affected component. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability has been found in Tongda OA 2017 up to 11.9 and classified as critical. Affected by this vulnerability is some unknown processing of the file general/project/proj/delete.php. The manipulation of the argument PROJ_ID_STR with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 12/29/2023. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2023-7180. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way. By approaching the search of inurl:general/project/proj/delete.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 11.10 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CNA Base Score: 5.5
CNA Vector (VulDB): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OA 2017 11.10
Timeline
12/29/2023 🔍12/29/2023 🔍
12/29/2023 🔍
03/19/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2023-7180 (🔍)
GCVE (CVE): GCVE-0-2023-7180
GCVE (VulDB): GCVE-100-249367
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/29/2023 23:20Updated: 03/19/2025 17:19
Changes: 12/29/2023 23:20 (44), 01/21/2024 19:45 (2), 01/21/2024 19:52 (28), 03/19/2025 17:19 (23)
Complete: 🔍
Submitter: zhengyi_
Cache ID: 216::103
Submit
Accepted
- Submit #254946: Beijing Tongda Xinke Technology Co., Ltd. tongdaOA Versions below v11.10 and v2017 SQL injection (by zhengyi_)
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.