# CVE-2026-4792: Bread <= 2.9.12 - Missing Authorization to Unauthenticated Information Exposure

> Unauthenticated attackers can retrieve plaintext PDF protection passwords via an unprotected settings export endpoint in the Bread WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-h866-wqgw-w5x9

## What is CVE-2026-4792?

CVE-2026-4792 is a medium-severity missing authorization vulnerability in radius314 Bread, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Bread plugin for WordPress is vulnerable to information exposure in versions up to and including 2.9.12. This is due to the lack of authentication and authorization checks on the settings export functionality (download_settings function) which is registered on the plugins_loaded hook and explicitly allows execution on non-admin (public) pages. The function exports all plugin configuration settings including the protection_password field, which is stored in plaintext. This makes it possible for unauthenticated attackers to retrieve the PDF protection password by accessing the /?export-meeting-list=1 endpoint.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-4792 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4792 is a medium-severity missing authorization vulnerability in radius314 Bread, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4792 in the wild and no public exploit code.

Affected product: radius314 Bread. 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-4792/ (Markdown: https://insights.sbomify.com/CVE-2026-4792/index.md)
```

## Sources

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

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