# CVE-2026-9013: Bogo <= 3.9.1 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via REST API

> Authenticated subscribers can expose sensitive content from private or password-protected posts via the Bogo plugin's REST API translation endpoint.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-4vf9-6whq-7g9v

## What is CVE-2026-9013?

CVE-2026-9013 is a medium-severity missing authorization vulnerability in rocklobsterinc Bogo, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Bogo plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.9.1 via the bogo_rest_create_post_translation. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract the raw title, content, excerpt, and password of any private, draft, or password-protected post by triggering its duplication via the translation endpoint and reading the returned title.raw, content.raw, and excerpt.raw fields of the duplicated post. This vulnerability is exploitable against posts written in a non-default locale, as authenticated subscribers can request a translation into the site's default locale to pass the locale-only permission gate. While subscribers can trigger the endpoint, this is only impactful at the Contributor-level as they can actually read the duplicated content.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-9013 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9013 is a medium-severity missing authorization vulnerability in rocklobsterinc Bogo, published on 19 Jun 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-9013 in the wild and no public exploit code.

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

## Sources

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

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