VDB-242909 · CVE-2023-45909 · EUVD-2023-50172

ZZZCMS 2.2.0 redirect

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.
4.7	$0-$5k	0.00

Summaryinfo

A vulnerability identified as problematic has been detected in ZZZCMS 2.2.0. The impacted element is an unknown function. The manipulation leads to redirect. This vulnerability is traded as CVE-2023-45909. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in ZZZCMS 2.2.0 (Content Management System). It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is integrity.

The weakness was shared 10/19/2023. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-45909 since 10/16/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1204.001 for this issue.

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-50172). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Content Management System

Name

ZZZCMS

Version

2.2.0

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.7

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.1
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Redirect
CWE: CWE-601
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/16/2023 🔍
10/19/2023 +3 days 🔍
10/19/2023 +0 days 🔍
02/13/2026 +848 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2023-45909 (🔍)
GCVE (CVE): GCVE-0-2023-45909
GCVE (VulDB): GCVE-100-242909
EUVD: 🔍

Entryinfo

Created: 10/19/2023 07:50
Updated: 02/13/2026 09:19
Changes: 10/19/2023 07:50 (35), 11/11/2023 09:30 (11), 02/13/2026 09:19 (15)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.