CVE-2023-5263
CVE-2023-5263 is a medium-severity vulnerability in Zzzcms with a CVSS 3.x base score of 6.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-275.
Key facts
- Severity: Medium (CVSS 3.x base score 6.3)
- CVSS v2: 6.5
- EPSS exploit prediction: 1% (46th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-275
- Affected product: Zzzcms
- Published:
- Last modified:
Description
A vulnerability was found in ZZZCMS 2.1.7 and classified as critical. Affected by this issue is the function restore of the file /admin/save.php of the component Database Backup File Handler. The manipulation leads to permission issues. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-240872.
Frequently asked questions
- What is CVE-2023-5263?
- A vulnerability was found in ZZZCMS 2.1.7 and classified as critical. Affected by this issue is the function restore of the file /admin/save.php of the component Database Backup File Handler. The manipulation leads to permission issues. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-240872.
- How severe is CVE-2023-5263?
- CVE-2023-5263 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
- Is CVE-2023-5263 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (46th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2023-5263?
- CVE-2023-5263 affects Zzzcms. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2023-5263?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2023-5263 published?
- CVE-2023-5263 was published on 2023-09-29 and last updated on 2026-06-17.
References
- https://github.com/yhy217/zzzcms-vul/issues/1
- https://vuldb.com/?ctiid.240872
- https://vuldb.com/?id.240872
Affected products (1)
- cpe:2.3:a:zzzcms:zzzcms:2.1.7:*:*:*:*:*:*:*
More vulnerabilities in Zzzcms
- CVE-2023-45554 — Critical (CVSS 9.8): File Upload vulnerability in zzzCMS v.2.1.9 allows a remote attacker to execute arbitrary code via modification of the…
- CVE-2020-19682 — High (CVSS 8.8): A Cross Site Request Forgery (CSRF) vulnerability exits in ZZZCMS V1.7.1 via the save_user funciton in save.php.
- CVE-2023-45555 — High (CVSS 7.8): File Upload vulnerability in zzzCMS v.2.1.9 allows a remote attacker to execute arbitrary code via a crafted file to…
- CVE-2020-19683 — Medium (CVSS 5.4): A Cross Site Scripting (XSS) exists in ZZZCMS V1.7.1 via an editfile action in save.php.
- CVE-2023-5582 — Low (CVSS 3.5): A vulnerability, which was classified as problematic, has been found in ZZZCMS 2.2.0. This issue affects some unknown…
Other CWE-275 vulnerabilities
- CVE-2017-6513 — Critical (CVSS 9.9): The WHMCS Reseller Module V2 2.0.2 in Softaculous Virtualizor before 2.9.1.0 does not verify the user correctly, which…
- CVE-2017-17060 — Critical (CVSS 9.8): OX Software GmbH OX App Suite 7.8.4 and earlier is affected by: Insecure Permissions.
- CVE-2017-16887 — Critical (CVSS 9.8): The portal on FiberHome Mobile WIFI Device Model LM53Q1 VH519R05C01S38 uses SOAP based web services in order to…
- CVE-2023-39399 — Critical (CVSS 9.1): Parameter verification vulnerability in the installd module. Successful exploitation of this vulnerability may cause…
- CVE-2023-39398 — Critical (CVSS 9.1): Parameter verification vulnerability in the installd module. Successful exploitation of this vulnerability may cause…
- CVE-2019-2177 — High (CVSS 8.8): In isPreferred of HidProfile.java in Android 7.1.1, 7.1.2, 8.0, 8.1 and 9, there is a possible device type confusion…