CVE-2026-4562 | MacCMS 2025.1000.4052 Timming API Endpoint Timming.php missing authentication
VulDBArchived Mar 22, 2026✓ Full text saved
A vulnerability was found in MacCMS 2025.1000.4052 and classified as critical . This affects an unknown part of the file application/api/controller/Timming.php of the component Timming API Endpoint . The manipulation results in missing authentication. This vulnerability was named CVE-2026-4562 . The attack may be performed from remote. In addition, an exploit is available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352399 · CVE-2026-4562 · GCVE-100-352399
MACCMS 2025.1000.4052 TIMMING API ENDPOINT TIMMING.PHP MISSING AUTHENTICATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.6 $0-$5k 1.94+
Summaryinfo
A vulnerability was found in MacCMS 2025.1000.4052. It has been classified as critical. This vulnerability affects unknown code of the file application/api/controller/Timming.php of the component Timming API Endpoint. This manipulation causes missing authentication. The identification of this vulnerability is CVE-2026-4562. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Detailsinfo
A vulnerability has been found in MacCMS 2025.1000.4052 and classified as critical. Affected by this vulnerability is an unknown code block of the file application/api/controller/Timming.php of the component Timming API Endpoint. The manipulation with an unknown input leads to a missing authentication vulnerability. The CWE definition for the vulnerability is CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. As an impact it is known to affect confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-4562. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. By approaching the search of inurl:application/api/controller/Timming.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.
Productinfo
Name
MacCMS
Version
2025.1000.4052
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
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: Missing authentication
CWE: CWE-306 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
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
03/22/2026 Advisory disclosed
03/22/2026 +0 days VulDB entry created
03/22/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: github.com
Status: Not defined
CVE: CVE-2026-4562 (🔒)
GCVE (CVE): GCVE-0-2026-4562
GCVE (VulDB): GCVE-100-352399
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 03/22/2026 09:25
Changes: 03/22/2026 09:25 (54)
Complete: 🔍
Submitter: HuajiHD
Cache ID: 99:188:101
Submitinfo
Accepted
Submit #775039: Maccms MacCMS 2025.1000.4052 Missing Authentication (by HuajiHD)
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸