| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in SeaCMS 12.9. The affected element is an unknown function of the file admin_weixin.php. This manipulation causes an unknown weakness. This vulnerability appears as CVE-2023-44172. There is no available exploit.
Details
A vulnerability was found in SeaCMS 12.9. It has been declared as problematic. Affected by this vulnerability is an unknown code of the file admin_weixin.php. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SeaCMS V12.9 was discovered to contain an arbitrary file write vulnerability via the component admin_weixin.php.
The weakness was presented 09/27/2023. The advisory is shared at github.com. This vulnerability is known as CVE-2023-44172 since 09/26/2023. Technical details are known, but no exploit is available.
By approaching the search of inurl:admin_weixin.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-48531). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/26/2023 🔍09/27/2023 🔍
09/27/2023 🔍
02/08/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-44172 (🔍)
GCVE (CVE): GCVE-0-2023-44172
GCVE (VulDB): GCVE-100-240433
EUVD: 🔍
Entry
Created: 09/27/2023 18:10Updated: 02/08/2026 18:38
Changes: 09/27/2023 18:10 (35), 10/19/2023 08:31 (11), 09/25/2024 13:07 (15), 02/08/2026 18:38 (2)
Complete: 🔍
Cache ID: 216::103
Submit
Duplicate
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.