SeaCMS 12.9 admin_ping.php privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.5$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in SeaCMS 12.9. This issue affects some unknown processing of the file admin_ping.php. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2023-44170. There is not any exploit available.

Detailsinfo

A vulnerability was found in SeaCMS 12.9 and classified as problematic. This issue affects some unknown functionality of the file admin_ping.php. Impacted is 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_ping.php.

The weakness was released 09/27/2023. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-44170 since 09/26/2023. Technical details of the vulnerability are known, but there is no available exploit.

By approaching the search of inurl:admin_ping.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-48529). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB 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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

09/26/2023 🔍
09/27/2023 +1 days 🔍
09/27/2023 +0 days 🔍
02/08/2026 +865 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2023-44170 (🔍)
GCVE (CVE): GCVE-0-2023-44170
GCVE (VulDB): GCVE-100-240431
EUVD: 🔍

Entryinfo

Created: 09/27/2023 18:10
Updated: 02/08/2026 16:32
Changes: 09/27/2023 18:10 (35), 10/19/2023 08:22 (11), 09/25/2024 13:07 (15), 02/08/2026 16:32 (2)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!