# CVE-2026-4562: MacCMS Timming API Endpoint Timming.php weak authentication

> Remote attackers can bypass authentication on the MacCMS Timming API endpoint due to missing authorization checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-jqqr-rw2r-w5cx

## What is CVE-2026-4562?

CVE-2026-4562 is a medium-severity missing authorization vulnerability in MacCMS, published on 22 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in MacCMS 2025.1000.4052. 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. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-4562?


## How do I fix CVE-2026-4562?

No fix has been published for CVE-2026-4562 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4562 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4562 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4562 and fix it if it is affected.

What it is: CVE-2026-4562 is a medium-severity missing authorization vulnerability in MacCMS, published on 22 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4562 exists.

Affected product: MacCMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4562/ (Markdown: https://insights.sbomify.com/CVE-2026-4562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4562
- OSV: https://osv.dev/vulnerability/CVE-2026-4562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4562/
Summaries are generated and may contain mistakes; the official description above is the record.