# CVE-2026-66724: Permission Bypass Via Undocumented HTTP Methods In MWDB Core

> Authenticated users can bypass capability checks to upload configs and blobs via undocumented HTTP methods in MWDB Core.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-8fv8-wffg-4323

## What is CVE-2026-66724?

CVE-2026-66724 is a medium-severity missing authorization vulnerability in CERT.PL MWDB Core, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MWDB Core versions >=2.0.0 and <2.19.0 contain a missing authorization vulnerability in the deprecated config and blob upload endpoints. These endpoints accept the undocumented POST method, which bypasses the capability checks applied to the documented PUT method. This allows any authenticated user without the adding_configs or adding_blobs capabilities to upload config and text blob objects to the system. The impact is limited to adding new config and blob objects. This issue has been fixed in version 2.19.0

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-66724 being exploited?

There is no known exploitation of CVE-2026-66724 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66724 is a medium-severity missing authorization vulnerability in CERT.PL MWDB Core, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66724 in the wild and no public exploit code.

Affected product: CERT.PL MWDB Core. 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-66724/ (Markdown: https://insights.sbomify.com/CVE-2026-66724/index.md)
```

## Sources

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

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